Closed squarefrog closed 2 years ago
Created a PR for this.
Could I ask if this is likely to make it into a tagged release soon? We've tried to update our pipeline to use our fork in the meantime, but this has been a failure as we also use Danger Xcode Summary, which doesn't use the fork.
I've tried updating that too, but I then get unexpectedCycle
errors from SPM. It doesn't seem like theres a nice way to use a fork right now.
Yes, I will make a release a soon as I come back from the holidays, if I manage to find a Mac even earlier 😁
Thank you, we appreciate it. Enjoy your well-earned rest 🌴
I've managed to get a Mac, and made a release (3.14.0). Please let me know if everything is OK :)
That is fantastic news thank you! I’ll update our ci servers Monday and keep an eye on them throughout the week.
We run iOS CI pipelines using
gitlab-runner
hosted on MacStudium Mac Minis. When two pipelines run at a similar time we get random failures resulting from our Danger step. Danger is setup as a nested Swift Package, which our CI server builds at the start of each pipeline run.When the runner clones the repo, it clones to a folder using the runner concurrency identifier. For example, here are two possible folders:
For the most part this works great, however we are getting failures related to the temporary directory Danger uses. Looking at two failed pipelines, I can see while the clone paths are different, the danger temporary path is the same:
Is there a way for us to define the temporary directory to use with Danger? That way we could just nest a
.tmp
folder within the clone directory.