Bitbucket Pipelines CI guide
Required CI pipeline, optional CoreAnalyzer configuration.
Requirements
- Bitbucket Pipelines enabled
- A secured repository variable named
COREDEVPRO_LICENCEcontaining only the CI licence issued on request
Steps
1
Enable Pipelines
Repository → Pipelines → Enable
Repository → Pipelines → Enable
2
Create the variable
Repository settings → Pipelines → Repository variables
Repository settings → Pipelines → Repository variables
COREDEVPRO_LICENCE = <key> (secured)3
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
bitbucket-pipelines.yml at the project root.• Download the optional configuration only when scope or thresholds need adjustment.
Keep the licence in the secured variable. The CLI identifies the repository from the checkout Git remote.
4
Review, then run
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. Run the pipeline and verify CLI
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. Run the pipeline and verify CLI
0.2.23 and the native coredevpro-report.cdp artifact.Finish
→
Download and unzip the artifact, then import
coredevpro-report.cdp or an explicitly requested JSON export in CoreAnalyzer.