Draft: (paused) Publish to GitLab container registry

• Move DOCKERFILE_PATH in the inherited docker block
• Define globally DOCKER_HUB_PATH variable
• Publish containers to GitLab Container registry
• Present docker jobs available only if based on a protected reference

Close #105.

assigned to @moul

added RN-silent label

added 3 commits

• dc5de91b - ci: Define globally DOCKER_HUB_PATH variable
• 367b3f8e - ci: Publish containers to GitLab Container registry (#105)
• 9471fe07 - ci: Present docker jobs available only if based on a protected reference

Compare with previous version

changed the description

added 1 commit

• e607a121 - ci: Present docker jobs available only if based on a protected reference

Compare with previous version

changed title from Publish to Gitlab container registry to Publish to GitLab container registry

added 4 commits

• 43dd3003 - ci: Move DOCKERFILE_PATH in the inherited docker block
• 3b86da7a - ci: Define globally DOCKER_HUB_PATH variable
• 9997447d - ci: Publish containers to GitLab Container registry (#105)
• 4cf5ca3c - ci: Present docker jobs available only if based on a protected reference

Compare with previous version

marked this merge request as draft

added C-cicd label

@pini-gh, @HugoTrentesaux, @tuxmain or anyone interested into the topic. I am thinking about having all containers published on GitLab Container Registry, since it doesn’t require a protected reference. And having the releases publish in addition to DockerHub. DockerHub would contain just the stable releases. What do you think about this publication design?

I would answer "why not?".

How is this gitlab container registry available for external users?

It’s publicly accessible here. You just have to specify the url when pulling the containers. Silkaj registry as an example.

It would be nice not to depend from an external proprietary service like dockerhub! Do we have to clear images manually or can we define an expiration date?

added 2 commits

• 633659f4 - ci: Publish containers to GitLab Container registry (#105)
• e8511d54 - ci: Present docker jobs available only if based on a protected reference

Compare with previous version

This needs to be rebased againsts current master branch.

changed title from Draft: Publish to GitLab container registry to Draft: (paused) Publish to GitLab container registry

mentioned in merge request !267 (merged)

unassigned @moul

@moul, you unassigned this MR. Should I close it and let #105 for an other MR?

Not a priority for me any more to have it in. Too much changes happen on .gitlab-ci.yml at the same when I was working on it. Today the rebase seems infeasible. Manually applying the changes from master would be a better solution. If someone (me included) would like to work in it later, this MR could be of help. Can be closed depending on how you want to manage this repo. Using only one of the two container registry would also be preferred, otherwise it means more maintenance. But, it has to be discuss.

Ok, so I keep this MR open with "(paused)" in the title to make the changes more visible for someone who wants to address #105.