Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by boleary-gl on Tuesday September 17, 2019 @02:20PM
(#20998431)
GitLab employee here.
Yes - if you bring your own runner to GitLab.com you can run unlimited build minutes on it - the build minutes we count are only those on our shared compute (2000 minutes for free, etc.).
The other huge benefit is that you can put that runner behind your firewall without poking any holes - itbjust needs access to GitLab.com and it can run your builds.
Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by jtwaleson on Tuesday September 17, 2019 @02:11PM
(#20998319)
Yes, have been doing this for a year in autoscaling configuration on gitlab.com
Edit: see https://docs.gitlab.com/runner/executors/docker_machine.html
Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by n42 on Tuesday September 17, 2019 @02:19PM
(#20998419)
You can also do this with Buildkite without having to drag along the rest of the cruft that is GitLab. It’s free for individuals, if I recall.
Buildkite is an excellent CI tool.
Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by mcintyre1994 on Tuesday September 17, 2019 @05:48PM
(#21000431)
Yep, we do this on GitLab.com - it’s one of the most well thought through systems I’ve worked with tbh. We use autoscaling EC2 spot instances for almost everything, incredibly cost efficient and unlimited.
Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by eblanshey on Tuesday September 17, 2019 @09:00PM
(#21001572)
Just curious how this works out for you? When I tried this, even when the spot bid was way above current price, it would often be stuck in a pending state since spot instances don't get created immediately. Do you get spot instances to be created immediately on demand somehow?
Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by mcintyre1994 on Wednesday September 18, 2019 @04:57AM
(#21003454)
Yep we see spot instances immediately created - there's no noticeable delay (compared to build times) against having permanent EC2 instances running. For our runners we want to use spot instances, the important part of the gitlab-runner register command are:
--executor docker+machine \
--machine-machine-driver amazonec2 \
--machine-machine-options "amazonec2-request-spot-instance=true \
--machine-machine-options "amazonec2-spot-price="
That last one means our bid defaults to the current on-demand price, which seems to get fulfilled immediately. FWIW we're using m4.large instances in eu-west-1a and according to the AWS UI the spot price has been perfectly consistent (at about 1/3 of on-demand) for at least the last 3 months so maybe that consistency is why it works so well for us.
Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by eblanshey on Sunday September 22, 2019 @01:34PM
(#21042636)
Thanks, I'll try this out! Has it ever happened that it doesn't get created immediately for whatever reason? And if that happens, will it automatically cancel the request and/or pipeline within X minutes, so that it doesn't randomly get fulfilled like a month later?
I thought this was possible, but after searching I was often confused. I imagine I'm using poor terms during my search. Thoughts?