Thanks @dkayiwa and @raff. I’ve seen this idea above to be easier to implement as making changes to some Bahmbo Plan branche’s stages/jobs tends to actually lead you to making changes on the Master Plan. I’ve applied this approach on the Event Module Plans.
I probably gave a bad example, but there are plenty of places where this is an issue. For example: Registration App module - Registration App module: Plan summary - OpenMRS Bamboo
Indeed @mseaton. Such should/will be carefully reconfigured.
I wanted to review your work, but the 3.x build doesn’t seem to be running in Docker yet. Please let me know once you have a draft build that we can look at and provide feedback.
@raff, I’ve added a Latest Bamboo plan to each of the Legacy UI, Calculation, and Event projects. The existing plans have been renamed to indicate the specific branches they track. For example, the Event Module 3.x plan now monitors the 3.x GitHub branch, while the new Latest plan monitors the master branch. I guess I should have used Master instead of Latest.
That said, I’ll continue to clone one of the above plans as a starting point for configuring other upgraded modules that are now using Java 21. However, both the Legacy UI and Calculation Module still exhibit reproducible failures with Java 21 outside the Bamboo environment, so I’ll need to investigate those issues further.
Newly created plans so far: