Description of the problem:
Optimize jobs have a strong dependency on the optimize shared library. Thus, when creating a maintenance branch, it should keep a reference to the current state of the shared library.
Desired outcome and acceptance tests:
- A given maintenance branch must refer to a specific version of the Optimize shared library.
- Multiple solutions here: a maintenance branch can also be created for the shared library. Alternatively, the current HEAD commit of the shared library can be written into the Jenkinsfile as a hard reference. The latter solution could be more feasible, as backporting patches for the shared lib might not happen so often.
- ideally, the solution is automatic - i.e. when a maintenance branch is created, a PR with the suggested change is automatically created. It can be implemented with GitHub Actions.