config value 'safe.directory' was not found (Rugged::ConfigError) error after upgrade to 0.11.1 about pronto HOT 8 CLOSED

In 0.11.0, the version of rugged used was more constrained. Maybe there's an incompatibility with the later versions with your CI -- can you try pinning it via gem 'rugged', '< 1.1.0' and see if it helps?

from pronto.

Thank you @ashkulz. Yes, if we pin rugged down it works again. Is this the best solution however?

from pronto.

@gingerlime the error is occurring at this line. Can you make a reproducible test case scenario or at least narrow which version of rugged is causing the issue?

from pronto.

@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.

from pronto.

@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 rugged version till they fix it, I'm not really sure I can do anything here 🤷‍♂️

from pronto.

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.

from pronto.

The best way is to pin rugged (during CI?) till their support responds with a solution. I've not got reports from anyone else, so I think it is something specific to their setup 🤷‍♂️

from pronto.

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.

from pronto.