Azure DevOps Pipelines

The Meterian Scanner Azure DevOps, available in the Azure DevOps Extensions Marketplace, adds an extra level of protection to your pipelines.
The native integration of Meterian in Azure DevOps can be completed in a few simple steps:
Install the Meterian Security Plus extension from the Marketplace
Set the Meterian API Token, either:
in a variables group
as part of a pipeline
In order to work, the Meterian scanner requires a working version of Docker in the image used to run the pipeline.
The only pre-requisite is a Meterian API Token which can be obtained from
your paid subscription account's Meterian Dashboard. If you are using a free account and would like to upgrade, contact [email protected].
​
Setting the Meterian API Token in variables group
Select Library from the Pipelines menu and create a new Variable group. Then add METERIAN_API_TOKEN  (click on the lock icon to make it as secret variable).
​
​
Specify the variable group in the pipeline (Option A)
1
# Starter pipeline
2
# Start with a minimal pipeline that you can customize to build and deploy your code.
3
# Add steps that build, run tests, deploy, and mode:
4
# https://aka.ms/yaml
5
​
6
trigger:
7
- main
8
​
9
pool:
10
 vmImage: 'ubuntu-latest'
11
    
12
variables:
13
- group: meterian-team-variables
14
​
15
​
Copied!
​
Setting the Meterian API Token as a pipeline variable (Option B)
From the Pipeline editor, click on Variable in the top right corner
​
Add Meterian task to the pipeline
In the Review section (or whenever editing the Pipeline) Click on "Show Assistant" and select "Meterian Scanner" from the list
The Meterian task must be under "steps" 
Save the Pipeline
1
trigger:
2
- main
3
​
4
pool:
5
 vmImage: 'ubuntu-latest'
6
    
7
variables:
8
- group: meterian-team-variables
9
​
10
steps:
11
- task: Meterian [email protected]
Copied!
Specifying options
It is possible to specify the Meterian CLI options and also to specify a custom working directory, neither of them is required.
1
steps: 
2
- task: Meterian [email protected]
3
  inputs:
4
    client_options: "--min-security=90"    
5
    working_directory: "$(Build.SourcesDirectory)/path/to/directory"
Copied!
A working example of pipeline can be found here.
You can also find here a non-native integration for Azure DevOps Pipelines

ONLINE INTEGRATIONS - Previous

Bitbucket Pipe

Next - Languages support

Introduction

Last modified 6mo ago

Copy link

Contents