Hello Paolo, the release jobs for repositories relying on kogito-pipelines framework will have the release jobs generated in respective non-main branches.
So after we branch 10.0.x, jobs for that given branch will be generated from DSL, among others nightly jobs but also the release jobs. If you're most familiar with drools, then you could start here. 1. Release job DSL: https://github.com/apache/incubator-kie-drools/blob/main/.ci/jenkins/dsl/jobs.groovy#L122 Jenkinsfile: https://github.com/apache/incubator-kie-drools/blob/main/.ci/jenkins/project/Jenkinsfile.release As you can see, the pipeline only builds other jobs, so you want to check also the "deploy" job, which is reused between nightly and release. 2. Deploy job DSL: https://github.com/apache/incubator-kie-drools/blob/main/.ci/jenkins/dsl/jobs.groovy#L253 Jenkinsfile https://github.com/apache/incubator-kie-drools/blob/main/.ci/jenkins/Jenkinsfile.deploy . Important thing to note, this job structure comes from kiegroup, so does not map 1-1 to what we need in ASF, but the deploy job itself should be fairly close to what we need, the Release job will most probably be reduced to the bare minimum, i.e. just triggering the Deploy job + some necessary preparations. That's why I was proposing we'd run a dry-run with a testing branch in the first place, so that we can check what gets generated when we branch :-) Regards Jan On Wed, 3 Jul 2024 at 11:55, Paolo Bizzarri <[email protected]> wrote: > Hello, > > I have finished the review of the steps related to Automation A of the > document on the release procedure. > > > https://docs.google.com/document/d/1t-08b970i9PMBy-TSM64x0RUH46pzwnIhEi-LVeL0lg/edit > > I am now looking at other parts that need to be moved - somehow. > > I can see the following automations are marked as needed for the release > and not completed: > > AUTOMATION D: Release candidate job on Jenkins > (this is marked as "Not implement and required to start the voting") > > AUTOMATION F: Git tag release jobs > AUTOMATION G: Artifacts release jobs > (these are marked as " Not implemented and required to release binaries > after voting") > > If the information is correct, the obvious next automation to complete is > Automation D - release candidate job on jenkins. > > The section for automation D is very very detailed on the packages to be > released, which is good. > > From the document itself and the jenkins, I can see that there is only one > job for the release, namely: > > > > https://ci-builds.apache.org/job/KIE/job/kie-tools/job/kie-tools-release-candidate/ > > I would say that we are missing - at least - all the jobs for the other > repos, namely: > - drools > - optaplanner > - kogito runtimes > - kogito apps > - kogito images > > So, if I got it correctly, we need to create the release jobs for these > other parts and review them. > > Feel free to tell me that I have misunderstood lots of stuff and that I am > completely off target. > > Meanwhile I will continue looking into the code and review docs and emails > to understand what we need to do next. > > Regards. > > Paolo >
