As we reevaluate how to best support and maintain Staging Ref in the future, we encourage development teams using this environment to highlight their use cases in the following issue: https://gitlab.com/gitlab-com/gl-infra/software-delivery/framework/software-delivery-framework-issue-tracker/-/issues/36.

Skip to content
Snippets Groups Projects
Commit d804a909 authored by Patrick Steinhardt's avatar Patrick Steinhardt
Browse files

Fix usage of out-of-date Gitaly images

Our CI jobs and docker-compose pull in the "latest" tag of Gitaly. As it
turns out though, "latest" is pointing to Gitaly v13.3.0-rc5, which is
definitely not the latest versionat this point in time. This is because
CNG was converted to not use the "latest" tag anymore, but instead to
use a tag called "master" in gitlab-org/build/CNG!519.

Fix this by using the new "master" tag instead.
parent 9d8a14e5
No related branches found
No related tags found
No related merge requests found
Loading
Loading
@@ -45,7 +45,7 @@ default:
- go version
- which go
services:
- name: registry.gitlab.com/gitlab-org/build/cng/gitaly:latest
- name: registry.gitlab.com/gitlab-org/build/cng/gitaly:master
# Disable the hooks so we don't have to stub the GitLab API
command: ["bash", "-c", "mkdir -p /home/git/repositories && rm -rf /srv/gitlab-shell/hooks/* && exec /usr/bin/env GITALY_TESTING_NO_GIT_HOOKS=1 /scripts/process-wrapper"]
alias: gitaly
Loading
Loading
Loading
Loading
@@ -3,6 +3,6 @@ services:
gitaly:
environment:
- GITALY_TESTING_NO_GIT_HOOKS=1
image: registry.gitlab.com/gitlab-org/build/cng/gitaly:latest
image: registry.gitlab.com/gitlab-org/build/cng/gitaly:master
ports:
- '8075:8075'
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment