CNG: CI overwrites release tags on feature branches for some images
When a feature branch is pushed (e.g. for PostgreSQL CNG image) the CI overwrites the production release tag with the image that is built for the branch. This is particularly dangerous when the feature branch contains any breaking change.
To avoid this, BUILDING_IMAGE
variable must be set to false
in ci_files/variables.yml
. The value needs to be changed after merging the branch which requires another change.
Several images have tag_and_push {X_VERSION}
{IMAGE_TAG_EXT}
- PostgreSQL
- kubectl
- Python
- Git
The problem is those jobs using tag_and_push
. If we change the postgres
Dockerfile in a feature branch, the CI for that branch would end up overwriting the docker image that is labelled with the PG_VERSION tag. That image would then be consumed all.