Avoid any push to become the production image

Maybe, instead of this, we can specify in config.toml a version number for the image instead of latest. Some scheme like

DOCKER_VERSION-

CI_BUILD_REF_NAME. This method creates an image per branch.

What's wrong with pushing to latest by default? It may also be confusing that nothing is going to populate the latest tag (which is used by docker when you don't specify a tag)

Maybe it could just be a suggestion in comment, e.g. "use the following instead to create a docker image tag per branch"? To be used only for users who understand what this means...

This is just to generate this image "gitlabci-docker-builder", not the imagfes it generates for the users.

The reason to do this change is that I was trying a change in another branch (docker-retry) it tried to push to latest, didn't work as script was empty, but having it worked I would have probably took down the runners, they use the latest tag.

added 3 commits

• f28d9caf - Add echo when replacing from
• 5ae752b0 - Update .gitlab-ci.yml for Gitlab patch requiring non empty scripts
• b8522ac0 - Avoid any push to become the production image

Compare with previous version

My bad, I got confused with the example we provide for building a docker image.

merged

mentioned in commit 352520e4