Re: [release] Aluminum code freeze
Thanh ha <zxiiro@...>
So a lot of this is actually automated and we have documentation on the branch cutting process here:
So there's a script that will update the JJB jobs templates to the next release but it is finicky. There's a few things it does wrong though including:
* Setting java-version for all projects but some csit jobs require "jre" instead of java-version.
* Duplicates the gerrit-release-merge jobs into the new branch causing JJB to fail due to duplicate job definition. This is something I can fix by moving release management jobs into their own project config. I'll look into this after branch cutting work is complete.
* Injects "java-version" to all jobs regardless of if they are java jobs at all so that needs to be manually resolved too.
* Does not appropriately update the opflex project (this is a snowflake project)
and a few other small things that need a human to inspect.
As for creating branches in all projects we have an autorelease job that will clone every repo and create stable/aluminium branches https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-branch-cut/ someone just has to manually run it once a release.
Finally the version bump job that we normally use needs to be run to bump the master branch.
So for the most part things are automated but there's a few steps that need a human to 1) decide when to run the job, and 2) inspect job config to fix issues caused by the jjb update script.
Regards,
Thanh
On Wed, Aug 5, 2020 at 3:16 PM Luis Gomez <ecelgp@...> wrote:
Not sure if this is tribal knowledge but every release I have to manually patch JJB for some misses:I have not checked yet the patch for this release.BR/LuisOn Aug 5, 2020, at 11:49 AM, Robert Varga <nite@...> wrote:On 05/08/2020 19:19, Luis Gomez wrote:Branching is not a problem, the real work is to update all the jenkins jobs after the branching. Some of them need special adjustments, not easy to automate today.
Well, for most projects I witnessed it's just a copy of the first block
-- do we have those specials documented somewhere, or is it just tribal
knowledge? :)
Thanks,
Robert