This is part of the work to switch our release engineering processes over to the "new-Jenkins" style jobs.
For now, it omits the platform and headnode builds and uses the old free-style jobs for those as we haven't finished converting them to new-style jobs. It does depend on us completing all of MANTA-4675 before the release builds will start, otherwise, I'll need more exceptions to the 'launch-build' script.
I haven't updated the documentation for the release process yet - specifically, I haven't mentioned that the release builds should all start automatically, which depends on how we get on with TOOLS-2362. Worst case, we get duplicate builds as a result of people following: https://modocs.joyent.us/engdoc/master/sdcrelease/index.html#step-5-run-jenkins-builds
I wonder should we have ls-missing-builds check for the presence of a release build-in-progress before starting one (or require a --force flag if we have one release build for this release already)
This is part of the work to switch our release engineering processes over to the "new-Jenkins" style jobs.
For now, it omits the platform and headnode builds and uses the old free-style jobs for those as we haven't finished converting them to new-style jobs. It does depend on us completing all of MANTA-4675 before the release builds will start, otherwise, I'll need more exceptions to the 'launch-build' script.
I haven't updated the documentation for the release process yet - specifically, I haven't mentioned that the release builds should all start automatically, which depends on how we get on with TOOLS-2362. Worst case, we get duplicate builds as a result of people following: https://modocs.joyent.us/engdoc/master/sdcrelease/index.html#step-5-run-jenkins-builds
I wonder should we have ls-missing-builds check for the presence of a release build-in-progress before starting one (or require a --force flag if we have one release build for this release already)