1 ‐ General Information

We set up a continuous integration (CI) with Jenkins. Two different jobs allow us

• to validate the HGCAL trigger primitives code in the package /L1Trigger/L1THGCal of the CMSSW framework (https://github.com/hgc-tpg/cmssw) using a validation suite from /HGCTPGValidation,

• to validate the validation code itself by applying it to a stable CMSSW release.

The CI workflow is the same for both jobs, it is described in the Jenkinsfile.

The validation of the CMSSW code consists of comparing two sets of results, a “reference branch” with a “test branch”. The reference branch corresponds to a stable version of CMSSW code, while the “test branch” corresponds to a code containing new developments or fixed code. In this case, the CI process is triggered by PullRequests (PR) into hgc-tpg/cmssw and each set is characterised by the PR properties (target and source branches in particular). The CMSSW release version is automatically detected from the target branch of the Pull Request. The same CMSSW release is used for the “reference” and for the “test” release.

The validation of the validation is triggered by a PR to the package /HGCTPGValidation (https://github.com/hgc-tpg/HGCTPGValidation). In this context, the same CMSSW release and the same remote/branch are set for both, reference and test, sets. These informations are given in the configuration file HGCTPGValidation/config/job_val_params.yaml.

The validation gives the possibilities to run over multiple configuration subsets. Each subset includes a pair of configurations, for the test and for the reference branches. The files defining the subsets and the configurations are in the directory HGCTPGValidation/config/.

Once the validation results are generated, they are displayed on a web page, available at the URLs:

• Validation page of the L1Trigger/L1THGCal of CMSSW => https://validation.llrhgcal.in2p3.fr/prod/
• Validation of the HGCTPGValidation code => https://validation.llrhgcal.in2p3.fr/valtest/