In order to start a new release cycle you need to be an administrator of both
cms-sw/cmsdist and have write privileges to jenkins (to setup IBs).
The following needs to happen:
CMSSW_X_Y_Zbranch in cms-sw/cmssw using the parent release series as a starting point. This is done by going to the main github page and clicking on the branch combo box.
IB/CMSSW_X_Y_Z/stablebranch in CMSDIST.
RELEASE_MANAGERSfor the new queue. cms-bot/releases.map and add the production architecture entry for the new release cycle
This is enough to setup releases. In order to have IBs you also need to.
SCRAM_ARCH: the architecture for the given IB.
PKGTOOLS_TAG: the PKGTOOLS branch to be used.
CMSDIST_TAG: the CMSDIST branch to be used.
RELEASE_QUEUE: the CMSSW branch to be used.
DISABLED: optional, if present, regardless of it’s value, the associated IB will be disabled. This means that jenkins will not schedule IBs for that release queue.
ADDITIONAL_TESTS: optional. Can have one or more of the following values, comma separated:
HLT: run special HLT tests
baseline: run baseline tests so that pull requests can be checked against this IB.
static-checks: run clang static analyser checks.
dqm-checks: run dqm specific checks.
build-any-ibin jenkins as well.
After setting up config.map,
build-any-ib in jenkins will build the IB as you configured it. You can use the parameters
tag-all-ibs to test your new IB.