Use dependency proxy in Developer Tooling projects

Problem

See DockerHub Limitations Mitigation - Coordination... (gitlab-org/gitlab#528723 - closed) for details.

TLDR: before April 1st, we need to enable the dependency proxy for images that would be pulled via CI from Docker Hub in projects that we own.

Projects

Project MR
gitlab-org/gitlab-development-kit> gitlab-org/gitlab-development-kit!4707 (merged)
gitlab-org/quality/tooling/gdk-stats> gdk-stats!26 (merged)
gitlab-org/ruby/gems/gitlab-dangerfiles> gitlab-org/ruby/gems/gitlab-dangerfiles!283 (merged)
gitlab-org/components/danger-review> gitlab-org/components/danger-review!19 (merged)
gitlab-org/components/gem-release> gitlab-org/components/gem-release!5 (merged)
gitlab-org/ruby/gems/gitlab-styles> gitlab-org/ruby/gems/gitlab-styles!257 (merged)
gitlab-org/quality/engineering-productivity/subparticle> gitlab-org/quality/engineering-productivity/subparticle!22 (merged)
gitlab-org/quality/engineering-productivity/pipeline-visualizer> gitlab-org/quality/engineering-productivity/pipeline-visualizer!24 (merged)
gitlab-org/quality/engineering-productivity/fast-quarantine> gitlab-org/quality/engineering-productivity/fast-quarantine!325 (merged)

Note

gitlab-dangerfiles and gitlab-styles used to be managed by EP. I’m unsure about current ownership, so I’m just updating them with this issue.

fast-quarantine is owned by groupdevelopment analytics but we’re doing it here to reduce their load.

Solution

Prefix image names in CI configs with ${GITLAB_DEPENDENCY_PROXY}.

Edited by Peter Leitzen