Update CI to support building a specific version through a triggered pipeline
The MR makes some fixes and changes to the CI pipeline in order to support building specific gitlab versions.
The idea is to support a triggered pipeline from both gitlab-ce and gitlab-ee. Those projects will trigger the pipeline and pass a few variables.
- Whether they want a CE or EE pipeline
- The gitlab rails version
- The gitlab shell version
- the gitaly version
What this MR does:
- Fix a bug where were weren't passing the correct gitlab-shell build arg to the gitaly container
- Include the component's tag/branch that we are going to build in its unique sha1 container tag (and cache-bust using it)
- When on CNG master, but building a component tag/branch other than master, push a container tag using the tag/branch name. (ie push the v10.8.0 tag in this repo if that's what we were triggered to build on master.)
- EE specific jobs are ignored if
CE_PIPELINE
is set, and CE specific jobs are ignored ifEE_PIPELINE
is set
What behaviour stays the same: Branch builds and the nightly schedule in this repo still build both CE and EE jobs. So nothing should really have changed for builds we are not triggering.
Edited by DJ Mountney