Use the following options to integrate Coverity into an ADO pipeline:
All-in-one Script
Add a traditional BAC script as a task in a job under ADO.Individual Tasks
Split each BAC step into separate tasks in a job under ADO.A Task Group -
Construct a template of tasks with variables as inputs that can be added directly to the job.Pipeline YAML file
CI as code, where the steps are specified in a YAML file, committed to SCM and called from the source repository.
Using a script
This method uses an all-in-one script to do the Coverity BAC as a single task.
...
|
Using tasks
This method is similar to the all-in-one script but it breaks each step into separate tasks and uses variables:
Create a New Pipeline
Enter Source Repository
Use Empty Job Template
Add the following, Under the Variables tab:
cov.authkey
cov.bin
cov.host
cov.idir
cov.stream
Add separate Command Line tasks to Job for
cov-build
,cov-analyze
andcov-commit-defects
.Cov-build
Code Block cov-build --dir $(cov.idir) mvn -B clean package -DskipTests
Cov-analyze
Code Block cov-analyze --dir $(cov.idir) --all --enable-callgraph-metrics --webapp-security
Cov-commit-defects
Code Block cov-commit-defects --dir $(cov.idir) --host $(cov.host) --auth-key-file $(cov.authkey) --stream $(cov.stream) --description $(Build.BuildURI) --target Windows_x86_64 --version $(Build.SourceVersion)
Using a task group
Newer versions of TFS support task groups that enable you to construct a set of tasks as per the above step, and then export as a JSON file that you can import into other build pipelines.
Using a YAML file
To set up a YAML based Coverity BAC, commit the following to your repository and then create a new build pipeline, selecting configuration as code and coverity.yml as the YAML source.
...