Re:GitLab Partners with DigitalOcean to make CI more affordable
by sytse on Tuesday April 19, 2016 @03:41PM
(#11529592)
This warning is outdated for the shared runners on GitLab.com since we do not reuse runners there at all. All runners are destroyed after a since build. Please see https://gitlab.com/gitlab-org/gitlab-ce/issues/14732 for more background and our effort to update this message.
Re:GitLab Partners with DigitalOcean to make CI more affordable
by explosion on Tuesday April 19, 2016 @04:09PM
(#11529864)
That's great to hear. Thanks.
Re:GitLab Partners with DigitalOcean to make CI more affordable
by mordocai on Tuesday April 19, 2016 @03:41PM
(#11529597)
We'd need an answer from gitlab, but that statement was there with the old infrastructure for shared runners.
It is possible that this issue is fixed with the new ones?
Re:GitLab Partners with DigitalOcean to make CI more affordable
by sytse on Tuesday April 19, 2016 @03:53PM
(#11529702)
You're correct, we fixed this issue, the new warning will be: "Shared runners execute code of different projects on the same Runner unless you configure GitLab Runner Autoscale with MaxBuilds 1 (which it is on GitLab.com)."
"GitLab Runners do not offer secure isolation between projects that they do builds for. You are TRUSTING all GitLab users who can push code to project A, B or C to run shell scripts on the machine hosting runner X."
Seems like a very strong reason to use one's own paid DigitalOcean instances for runners instead of using the free shared runners, at least for commercial projects. I was wondering if anyone from GitLab could expand further on this?