Build tagged images on git tags

Currently our workflow looks like this:

release-image:
  stage: deploy
  script:
    - docker build -t "$CONTAINER_RELEASE_IMAGE"
      --build-arg DJANGO_ENV=production -f docker/django/Dockerfile .
    - docker push "$CONTAINER_RELEASE_IMAGE"
  only:
    - master
  environment:
    name: production  # used to track time with 'cycle analytics'

Where CONTAINER_RELEASE_IMAGE equals to "$REGISTRY/$GROUP_NAME/$PROJECT_NAME:latest".

But, that an anti-pattern. Because we always use latest for version numbers. There’s no default way to build versioned images like: "$REGISTRY/$GROUP_NAME/$PROJECT_NAME:3.5".

And I suggest to fix it with git tag. I already use it in our workflow, we just need to set appropriate tag names when new tag is pushed. We can use CI_COMMIT_TAG with a simple condition. https://docs.gitlab.com/ee/ci/variables/

[sobolevn]

This might help to integrate several services together. There are usecases when other images require different image versions.

Like microservices, frontend/backed, etc. I will experiment with it soon enough.

[AlwxSin]

I’d also suggest to use anchors like this

.release-image: &release-image
  stage: deploy
    script:
    - docker build -t "$CONTAINER_RELEASE_IMAGE:$TAG_NAME"
      --build-arg DJANGO_ENV=production -f docker/django/Dockerfile .
    - docker push "$CONTAINER_RELEASE_IMAGE:$TAG_NAME"
  environment:
    name: production  # used to track time with 'cycle analytics'


# Releasing image, when tests pass (only one at a time):
release-latest-image:
  <<: *release-image
  variables:
    TAG_NAME: latest
  only:
    - master
    
release-tagged-image:
  <<: *release-image
  variables:
    TAG_NAME: $CI_COMMIT_TAG
  only:
    - tags