GitLab Partners with DigitalOcean to make CI more affordable
about.gitlab.com
GitLab Partners with DigitalOcean to make CI more affordable
1–10 of 138 posts
Re: GitLab Partners with DigitalOcean to make CI more affordable
#2> GitLab partnered with DigitalOcean to provide free Runners to all projects on GitLab.com
Wow, I hope that doesn't get abused and taken away.
Re: GitLab Partners with DigitalOcean to make CI more affordable
#3> GitLab partnered with DigitalOcean to provide free Runners to all projects on GitLab.com Wow, I hope that doesn't get abused and taken away.
We hope so too, hopefully we can keep offering this for a long time, like we offer public and private repositories.
Re: GitLab Partners with DigitalOcean to make CI more affordable
#4> GitLab partnered with DigitalOcean to provide free Runners to all projects on GitLab.com Wow, I hope that doesn't get abused and taken away.
They should probably rate limit in a sensible way.
Re: GitLab Partners with DigitalOcean to make CI more affordable
#5For more information about the autoscaling see https://about.gitlab.com/2016/03/29/gitlab-runner-1-1-releas... Questions about anything GitLab are very welcome.
Re: GitLab Partners with DigitalOcean to make CI more affordable
#6In the shared runner settings, I see this:
"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?
Re: GitLab Partners with DigitalOcean to make CI more affordable
#7In the shared runner settings, I see this: "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 projec…
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
#8In the shared runner settings, I see this: "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 projec…
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
#9Came here to post it, but too late! Good job @fweespee_ch!
The importance of this announcement is that DigitalOcean is all over Fortune 500, and GitLab partnership means that Git is not only mainstream - it's THE stream.
Re: GitLab Partners with DigitalOcean to make CI more affordable
#10Came here to post it, but too late! Good job @fweespee_ch! The importance of this announcement is that DigitalOcean is all over Fortune 500, and GitLab partnership means that Git is not only mainstream - it's THE stream.
> DigitalOcean is all over Fortune 500
Do you have any reference for that? I was under the impression that DigitalOcean was mostly used by developers and startups. I was also under the impression that Git became the mainstream VCS a while ago...