The current naming scheme for the jenkins job uses the template: container-builder_<github org><repo><branch or tag> template, e.g. container-builder_IEMS-SDS_swot-pcm_develop. In a shared CI development environment, when multiple developers register a jenkins job for their cluster for the same repo and branch, they end up trying to clobber the previous jenkins job which can lead to permission issues on the CI instance but more importantly redirects the publish location to a different cluster.
Task is to ensure jenkins job uniqueness by prepending venue name to the jenkins job name.
The current naming scheme for the jenkins job uses the template:
container-builder_<github org><repo><branch or tag>
template, e.g.container-builder_IEMS-SDS_swot-pcm_develop
. In a shared CI development environment, when multiple developers register a jenkins job for their cluster for the same repo and branch, they end up trying to clobber the previous jenkins job which can lead to permission issues on the CI instance but more importantly redirects the publish location to a different cluster.Task is to ensure jenkins job uniqueness by prepending venue name to the jenkins job name.