[GCP] Tagging images is not following common approach
For images that are created during the release process we get tags in the following format:
v0-14-2-e8bfd98c
, v0-14-2-v0.14.2
.
It is not a common approach - for example, v0.14.2
, and it causes issues with the GCP infra release process, as our scripts are based on this general format - vX.X.X
.
Could you please share your concerns about why this predefined variable $CI_COMMIT_REF_SLUG
is used in the containerize jobs?
export EXTRA_DOCKER_TAG=""; if [ "$CI_COMMIT_TAG" != "" ] ; then EXTRA_DOCKER_TAG="-t $CI_REGISTRY_IMAGE/osdu-gcp-$SEISMIC_OSDU_GCP_SERVICE:$CI_COMMIT_REF_SLUG-$CI_COMMIT_TAG" ; elif [ "$CI_COMMIT_REF_NAME" = "master" ] ; then EXTRA_DOCKER_TAG="-t $CI_REGISTRY_IMAGE/osdu-gcp-$SEISMIC_OSDU_GCP_SERVICE:latest" ; fi
It would be great if you could refactor this part of the jobs in the pipelines.