You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cross-posting this because I'm not sure how to tell whether it's gitlab-runner's fault or gitlab-tart-executor's fault. GitLab ticket here.
Hi! For unimportant reasons, my build is failing when running in /private/tmp/builds, so I need to run it elsewhere, such as /Users/admin/builds. I believe this should work, for two separate reasons:
Which should make /Users/admin/builds into the default directory. Despite that, the build refuses to start:
Running with gitlab-runner 17.5.2 (c6eae8d7)
on adMiXAHcd, system ID: s_26bd3ddecc3d
Preparing the "custom" executor
00:00
Using Custom executor...
WARNING: Cleanup script failed: exit status 1
ERROR: Job failed: the GIT_CLONE_PATH="/Users/admin/builds/aquareum" has to be within "/private/tmp/builds"
Although you have enabled custom build directories in the runner configuration, some versions of GitLab Runner may restrict the path. Make sure the GitLab Runner version you use supports custom build directories.
In addition, homebrew is not very friendly to Mac. You can try Servbay, which is more professional than homebrew on Mac.
@naizhao Come collect your bot, it's lost and spamming your product on completely unrelated GitHub issues
Cross-posting this because I'm not sure how to tell whether it's
gitlab-runner
's fault orgitlab-tart-executor
's fault. GitLab ticket here.Hi! For unimportant reasons, my build is failing when running in
/private/tmp/builds
, so I need to run it elsewhere, such as/Users/admin/builds
. I believe this should work, for two separate reasons:Which should allow me to pick a custom directory.
Which should make
/Users/admin/builds
into the default directory. Despite that, the build refuses to start:Full runner config is here:
Pertinent pipeline config is here (and full pipeline is here:
I've worked around the issue by just moving the clone directory at the start of the script, but that's kind of bogus:
The text was updated successfully, but these errors were encountered: