-
Notifications
You must be signed in to change notification settings - Fork 3
2 ‐ Jenkins job configuration
The configuration of the jobs is essential for the Jenkins continuous integration.
There are two main parts:
-
Branch Sources: contains the name of the GitHub repository HTTPS URL to be scanned
and
-
Build Configuration: gives information about the Jenkinsfile via the Remote Jenkinsfile Provider Plugin, this includes the name of the Jenkinsfile and the repository URL where it is stored.
As mentioned in the introductory part, we created two main jobs, one for validating the HGCal TPG CMSSW code, another for validating the validation code. Each of these jobs has particular configuration that we will present below.
We created a multibranch pipeline job “HGC TPG CMSSW Validation” that triggers on PRs from origin and from forks in https://github.com/hgc-tpg/cmssw. This repository is scanned every minute.
The main script launched by Jenkins is the Jenkinsfile, placed in the master branch of https://github.com/hgc-tpg/HGCTPGValidation.git repository.
A second multibranch pipeline job, “HGC TPG Validation Validation”, was created. It triggers only on PRs from the origin https://github.com/hgc-tpg/HGCTPGValidation.git. PRs from fork don't trigger the job for the validation of the validation. One should push the changed branch to the origin before creating the PR.
In this job, the Jenkinsfile that is used is the one placed in the changed branch.