Azure DevOps CI guide
Required CI pipeline, optional CoreAnalyzer configuration.
Requirements
- A secret
COREDEVPRO_LICENCEvariable containing only the CI licence issued on request - A YAML pipeline using an
ubuntu-latestagent
Steps
1
Create the secret variable
Pipeline → Edit → Variables → New variable, then select “Keep this value secret”
Pipeline → Edit → Variables → New variable, then select “Keep this value secret”
COREDEVPRO_LICENCE = <your_key> (secret)2
Add the pipeline
• Download the verified pipeline, then save it as
• Download the optional configuration only when scope or thresholds need adjustment.
• Download the verified pipeline, then save it as
azure-pipelines.yml at the repository root.• Download the optional configuration only when scope or thresholds need adjustment.
Keep the licence in the secret variable. The CLI identifies the repository from the checkout Git remote.
3
Review the scope, then configure only if needed
Keep the defaults when the scope is correct. Optional configuration can adjust duplication thresholds and explicit file exclusions. CoreAnalyzer handles native technical exclusions, and tests should not be excluded by default.
Keep the defaults when the scope is correct. Optional configuration can adjust duplication thresholds and explicit file exclusions. CoreAnalyzer handles native technical exclusions, and tests should not be excluded by default.
4
Run
Run the pipeline. Verify Node.js 20, CLI
Run the pipeline. Verify Node.js 20, CLI
0.2.23 and the native coredevpro-report.cdp. The report is published even when the critical quality gate fails.Finish
→
Download and unzip the artifact, then import
coredevpro-report.cdp or an explicitly requested JSON export in CoreAnalyzer.