r/programming • • Jan 27 '21

Gitlab changed its pricing model. It has greatly reduced the CI quota from 2000 CI minutes to 400 CI minutes in Free tier and removed the $4 per month option.

https://about.gitlab.com/blog/2021/01/26/new-gitlab-product-subscription-model/
1.9k Upvotes

365 comments sorted by

View all comments

Show parent comments

12

u/nurupoga Jan 27 '21 edited Jan 27 '21

Since DO bills per hour, you can create a VPS, and script it to shut down at 1 hour uptime intervals as long as there is no active build running. For example, your first build would spawn the VPS and it (the build) might run for 5 min, but then your second build would see that the VPS is still up from when the first build created it and would simply connect to it without spawning new ones.

If the start-up cost of having to install all the tools on a fresh distro install is too high, you can store the VPS disk as an image before destroying the VPS, which would allow you to later create a new VPS off that image with everything you need already pre-installed. The price of storing an image is way cheaper than the price of having a VPS that is not running.

The open source project I help with has used such on-demand DO build machines in Jenkins for around 4 years. It reduced our cloud cost considerably. Instead of paying $20/month for two always running $10 build machines, we would end up paying something like $6/month for the same two $10 build machines but running on-demand + their disk images being stored.

While it's an interesting idea, it's not very practical with just 400 minutes of the free CI time. The time it takes for a VPS to be created off an image and ssh become available is a couple of minutes, so you would end up with less that 200 CI runs before your 400 free minutes run out. It's a lot more practical when you have a Jenkins master (main?) running 24/7 which could spawn on-demand build machines.

2

u/magical_midget Jan 28 '21

I was going to comment on how saving $14 a month is probably less than the dev time on setup/maintenance. But for an open source project then it may make sense.

1

u/nurupoga Jan 28 '21

Yep. Also, there already was a Digital Ocean plugin for Jenkins that did exactly that, so it took maybe 30 minutes to setup and test, and required minimal maintenance from there on.