Hello, this is the report of the successul verification of the automation code for the release of Apache Kie Kogito Images.
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 that validates the images and updates the modules descriptors . Release document. https://docs.google.com/document/d/1t-08b970i9PMBy-TSM64x0RUH46pzwnIhEi-LVeL0lg/edit Relevant code https://github.com/apache/incubator-kie-kogito-images/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 42-48 of the setup file *** undocumented step *** for this repo, the script validates the images and updates the modules descriptors. this happens at lines 69-76 "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 106-108 of the setup file . The commit message is different. git push origin [input New branch name] Line 109 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
