L3 - Default Problem
- The Docker QA job uses maven to change the version (e. g. from 7.14.0-SNAPSHOT to 7.13.0-ee)
- The maven project fails with the error attached: docker-qa-maven-error.txt
Reasoning
Right after the minor/patch release, the snapshot artifact of the next development version hasn't been built and uploaded to nexus.
Solutions
- Do not set the version via maven command; Use a shell script to set the version instead
- Integrate the job into the release pipeline so that it can consume the local maven repository
- A reason against it could be that the release should not fail when there is a problem with the Docker QA images
- Make Docker QA module independent of the maven hierarchy
Anti-Solution
Checking out the tag is not an option since the tagged versions camunda-bpm-platform-ee are lacking the -ee suffix
Decision
Solution #3 was selected
Reasoning
- Solution #3 is more robust than solution #1
- Solution #2 would fail the release in case of a problem with the Docker QA images