Jenkins CI guide
Required Jenkinsfile, optional CoreAnalyzer configuration.
Requirements
- Jenkins with a Linux agent
- A secret text credential named
COREDEVPRO_LICENCEcontaining only the CI licence issued on request
Steps
1
Create the credential
Manage Jenkins → Credentials → Global → Add Credentials
Manage Jenkins → Credentials → Global → Add Credentials
Kind = Secret text; ID = COREDEVPRO_LICENCE; Secret = <your_key>2
Add the Jenkinsfile
• Add the supplied
• Add
• Add the supplied
Jenkinsfile at the repository root.• Add
coredevpro_config.yml only when scope or thresholds need adjustment.Keep the licence in the secret credential. The Jenkinsfile fills
X-REPO from JOB_NAME.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
Build
Run a build. Verify that
Run a build. Verify that
project.zip was created and report.json was generated by default. 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.