Open radtriste opened 12 months ago
One thing to consider here is that when we push the branch of kogito-pipelines, a new image for given branch starts building (as for 10.0.x).
But if we immediately started generating jobs for that branch, it could lead to this image not being yet available (as it takes time, queues might be long).
Luckily we have some control on timing of a) pushing 10.0.x into kogito-pipelines (which triggers image build automatically) b) updating .ci/jenkins/config/main.yaml with 10.0.x (which triggers the job generation automatically)
What we're missing in the list is x) adjusting .ci/jenkins/config/branch.yaml in 10.0.x pointing at correct image tag
And finding a proper place for it in the pipelines flow.
Field
jenkins.agent.docker.builder.image
in the branch config should reference the branch image builder. That means, when branching, to update that file and create the new builder image (simple docker tag/push should do it.)