AT:
- every jenkins job (excluding initial-seed-job and seed-job-optimize) can be configured such that the branch is specified to run the job with
Context:
There are jenkins jobs e.g. release job that to now allow to set the branch as a parameter.
AT:
Context:
There are jenkins jobs e.g. release job that to now allow to set the branch as a parameter.
This job updated to now take branch parameter:
https://ci.optimize.camunda.cloud/view/all/job/dependency-check/
The only non-parameterized jobs are now these two seed jobs:
https://ci.optimize.camunda.cloud/view/all/job/initial-seed-job/
https://ci.optimize.camunda.cloud/view/all/job/seed-job-optimize/
johannes.heinemann - do we want these two parameterized as well? I'm not totally sure of the purpose/benefit