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
• Add the supplied
• Add
• Add the supplied
bitbucket-pipelines.yml at the project root.• Add
coredevpro_config.yml only when scope or thresholds need adjustment.Keep the licence in the secured variable. The step fills
X-REPO from BITBUCKET_REPO_FULL_NAME.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 the project archive and 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. Run the pipeline and verify the project archive and default
report.json artifact. Signed or encrypted .cdp output is available in compatible CLI workflows.Finish
→
Download and unzip the artifact, then import the generated JSON or .cdp file in CoreAnalyzer.