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 workflow
• Add the supplied
• Add
• Add the supplied
.gitlab-ci.yml at the project root.• Add
coredevpro_config.yml only when scope or thresholds need adjustment.Keep the licence in the protected, masked variable. The job fills
X-REPO from CI_PROJECT_PATH.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 the project archive and the default
Commit and push. In Jobs, verify the project archive and the default
report.json artifact. For CLI workflows, signed or encrypted .cdp output is available when enabled by the active access.Finish
→
Download and unzip the artifact, then import the generated JSON or .cdp file in CoreAnalyzer.