Hello, this is the report of the successul verification of the automation code for the release of Apache Kie Optaplanner.
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. Release document. https://docs.google.com/document/d/1t-08b970i9PMBy-TSM64x0RUH46pzwnIhEi-LVeL0lg/edit Relevant code https://github.com/apache/incubator-kie-optaplanner/tree/main/.ci/jenkins Steps verified for Automation A "Git clone one of the 7 repos @ development branch (E.g., `main`) NOTE: incubator-kie-sandbox-quarkus-accelerator’s development branch is `0.0.0`, not `main`" *** It is unclear where this step is performed *** "git checkout -b [input New branch name] NOTE: incubator-kie-sandbox-quarkus-accelerator’s new development stream branch should be major.minor.999, instead of major.minor.x." Lines 48-56 of the setup file "Do a D commit by running the configured scripts (updating own and upstream dependencies versions) NOTE: On `kie-tools`, the new version is major.minor.999, while on Maven-based repos, the new version is major.minor.999-SNAPSHOT. E.g., 10.0.999 and 10.0.999-SNAPSHOT." git commit --allow-empty -am "Update development version to [new version]"." Lines 78-85 of the setup file . The commit message is different. git push origin [input New branch name] Line 86 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
