-
Notifications
You must be signed in to change notification settings - Fork 246
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
config value 'safe.directory' was not found (Rugged::ConfigError) error after upgrade to 0.11.1 #440
Comments
In |
Thank you @ashkulz. Yes, if we pin |
@gingerlime the error is occurring at this line. Can you make a reproducible test case scenario or at least narrow which version of |
@ashkulz yeah, I saw the line where it fails, but I'm not sure how to reproduce it. It seems something internal to git and how rugged is accessing git data. I'm entirely unfamiliar with this unfortunately. As I mentioned it only happens on Semaphore. I can ask the Semaphore support team however. Maybe they have an idea. |
@gingerlime doing a quick google search tells that the permissions on the git directory in SemaphoreCI are incorrect -- e.g. see this discussion. I think you should pin the |
Thanks @ashkulz yeah, I found this discussion as well, but I don't see any permission issues on Semaphore. I tried to debug it and it looked ok to me. I contacted their support, so let's see what they say. But I can imagine them saying "it's Rugged. The new version broke things", so it's something in-between the two :) I understand also pronto is in-between here, but I hope we can find a solution together. I'd be happy to test whatever I can and also hope that Semaphore is able to help. I appreciate you taking the time to look into it. |
The best way is to pin |
It might be specific to Semaphore, so that's definitely good to know. Let's see what they say and take it from there :) thanks again for your patience and assistance. |
We're seeing a weird error, which seems to happen only on our CI but not on local development:
Our CI (Semaphore) seems to use some kind of a shallow clone of our github repository, but we fetch all the code as far as I can tell. Not sure what else might be the difference. File permissions seem fine. It's consistently failing on Semaphore but works on our local dev environment somehow.
Our semaphore yml looks like this (redacted with the key commands)
It works 100% consistently with pronto 0.11.0
Any suggestions? :)
The text was updated successfully, but these errors were encountered: