Skip to content

README: update part about cache problem with ticket link #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nafg wants to merge 1 commit into
base: master
Choose a base branch
from
Open

README: update part about cache problem with ticket link #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,8 @@ gcloud --project $PROJECT_ID compute ssh gitlab-ci-runner-as-1

## Unresolved

I still haven't found out why the Cache is not working properly, it might be the way the
Gitlab Runner currently handles Google Cloud Storage endpoint with the S3 compatibility mode.
I'll try to find time to fork the runner repository and rewrite the minion cache client to use the latest information
of how the GCS wants to handle the interoperability communication.
Google Cloud Storage is not currently supported by the distributed cache, even though it has an S3 compability mode. There's a ticket about that [here](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/1773), which says

> Google Cloud Storage runs an older version of the S3 protocol that doesn't work well with the caching configuration.

and a WIP merge request [here](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/447).