Hello, this is the report of the successul verification of the automation code for the release of Apache Kie Kogito Apps.
I have checked that what is in the document for the release is implemented in the jenkins files. Summary of findings: - The commit message is different. - It is unclear to me where the clone step is performed - It is unclear how the Automation B and C are connected. - there is an extra step for checking out the drools and kogito runtime repos, that are also built in two successive steps. Release document. https://docs.google.com/document/d/1t-08b970i9PMBy-TSM64x0RUH46pzwnIhEi-LVeL0lg/edit Relevant code https://github.com/apache/incubator-kie-kogito-apps/blob/main/.ci/jenkins/Jenkinsfile.setup-branch Steps verified for Automation A "Git clone one of the 7 repos @ development branch (E.g., `main`) *** It is unclear where this step is performed *** "git checkout -b [input New branch name] Lines 30-40 of the setup file Note that both the kogito runtimes and the drools repository are checked out during this step. *** undocumented steps *** for this repo, the script first builds the drools repository. this happens at lines 46-53 then the script builds the kogito-runtime repository. this happens at lines 60-67 "Do a D commit by running the configured scripts (updating own and upstream dependencies versions) git commit --allow-empty -am "Update development version to [new version]"." Lines 89-92 of the setup file . The commit message is different. git push origin [input New branch name] Line 93 of the setup file. It is unclear how the Automation B and C are connected. This completes the verification of the steps indicated. Regards Paolo
