GitLab CI guide
Required CI workflow, optional CoreAnalyzer configuration.
Requirements
- A protected and masked
COREDEVPRO_LICENCEvariable containing only the CI licence issued on request - A Linux x64 runner
Steps
1
Create the protected variable
Settings → CI/CD → Variables → Add variable
Settings → CI/CD → Variables → Add variable
COREDEVPRO_LICENCE = <key> (protected, masked)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
.gitlab-ci.yml at the project root.• Download the optional configuration only when scope or thresholds need adjustment.
Keep the licence in the protected, masked 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. In an optional
Keep the defaults when the scope is correct. In an optional
coredevpro_config.yml, limit changes to useful thresholds and explicit exclusions:- Duplication:
duplicate_thresholdwithmin_linesandmin_characters - Files:
ignore_dirsandignore_files - CoreAnalyzer handles native technical exclusions automatically.
- Tests can provide usage evidence; do not exclude them by default.
4
Run
Commit and push. In Jobs, verify that CLI
Commit and push. In Jobs, verify that CLI
0.2.23 ran and that the native coredevpro-report.cdp is available. The report is preserved 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.