Jenkins CI guide
Required Jenkinsfile, optional CoreAnalyzer configuration.
Requirements
- Jenkins with a Linux agent, Node.js 18+ and npm
- 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
• Download the verified Jenkinsfile, then save it as
• Download the optional configuration only when scope or thresholds need adjustment.
• Download the verified Jenkinsfile, then save it as
Jenkinsfile at the repository root.• Download the optional configuration only when scope or thresholds need adjustment.
Keep the licence in the secret credential. 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. 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 Node.js, npm, CLI
Run a build. Verify Node.js, npm, CLI
0.2.23 and the native coredevpro-report.cdp. The report is archived 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.