-
Notifications
You must be signed in to change notification settings - Fork 12
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.
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
GitLab CI fails whenever repo is not public #267
Comments
Does it work on a public repository? Can you provide the cli used to register the runner? How did you get your token? It's weird because it works at home™. |
It does work on a public repo, and it does work when GitLab is not installed alongside YunoHost. I used the interactive registration and am using the docker executor. Right now, I'm using the docker image GitLab provides (gitlab/gitlab-runner), but the issue also existed for me when I used the GitLab runner provided by the app catalog. I got the token by going through Admin > CI/CD > Runners > New instance Runner. I reinstalled GitLab a number of times, and tried modifying various nginx configs just to see if anything would change, but nothing did change. I reset everything back, and it still doesn't work. Let me know if there are any more logs I can provide - I am honestly at a loss at this point, none of the logs I went through gave me any idea of why it isn't working for me. |
Ok, I spoke too fast, I can reproduce your issue on my server. It'll be way easier for me to debug. It's probably because of the Yunohost's sso. |
I manually fix this issue by hacking the ssowatt conf file and adding to If you don't know what I'm talking about, just wait the next release ;) |
works perfectly for me, thank you! |
FYI, the conf will be overwritten on each app install/upgrade/remove |
Describe the bug
After setting up a GitLab runner, whether managed through YunoHost or not, any and all build jobs on a non-public repo fail as soon the runner attempts to pull your repo.
Context
Steps to reproduce
Expected behavior
The runner should pull your repo using an authentication token. The runner does attempt to use the token, but it seems like something is stopping GitLab from seeing this token - I can't find any log containing the ci-runner:token@gitlab I expected. I do find two 401s in the rails production logs matching up to the build job, though.
Logs
GitLab CI log:
/var/log/gitlab/gitlab-rails/production_json.log:
The text was updated successfully, but these errors were encountered: