News for hackers. Stuff that matters.
Re:Shifting Gears by Boxxed on Monday September 03, 2018 @01:08PM (#17903684)
Last I used Gitlab CI I remember being somewhat infuriated at the fact that I couldn't use the Gitlab docker repo as the source for my build images. That was about a year ago though so that might be old news.
Re:Shifting Gears by tmaczukin on Monday September 03, 2018 @02:18PM (#17904087)
You can use images hosted on GitLab's Container Registry. Especially - you can use such images as the base for CI/CD jobs running on the same GitLab instance.

It was possible since very erly state of GitLab's Container Registry. The problem was when one wanted to use images created from internal or private projects, which require previous authentication. Support for such workflow was added (partially) in GitLab Runner 0.6, and with GitLab Runner 1.8 (late 2016) it's possible to use any private registry with GitLab CI jobs. And private images from the same GitLab instance are accessible without any additional work that needs to be made by the user - until the user who triggered a job has access to the project where requested image is stored.

Details can be found at https://docs.gitlab.com/ee/ci/docker/using_docker_images.htm....

Re:Shifting Gears by sytse on Monday September 03, 2018 @01:54PM (#17903948)
Not sure I understand your request but you can use docker images as part of your build https://docs.gitlab.com/ee/ci/docker/using_docker_images.htm...