Live data from Hacker News

Gitlab reducing free tier CI/CD minutes from 2000 to 400 minutes

about.gitlab.com

161–170 of 176 posts

Re: Gitlab reducing free tier CI/CD minutes from 2000 to 400 minutes

#161

One thing that always confuses me about the business factors in this kind of announcement, where they say that the vast majority of users won't be effected: > We evaluted CI/CD minute usage and found that 98.5% of free users use 400 CI/CD minutes or less per month. Okay, so just that 1.5% of free users, each using at most 1600 minutes more than the 400 under the new limits... is enough cost to actually matter and mak…

Worth thinking about this in the context of fat-head vs. long-tailed distributions, or less formally "whales". A very small number of users (the "head" or "whales") can account for most of the area under the curve, which in this case is the cost of delivering free build minutes.

For a toy example, imagine one user uses 2k minutes, 10 use 100 minutes, and 1000 use 1 minute. In this case you have "Over 99% use 100 minutes or less", but 50% of your cost is going to the one 2k minute user.

I have no idea if this is their exact curve, just showing how a fat-head distribution could explain what they are saying. I'd expect the "demand" (i.e. minutes used if they were not constrained / all paid for) to be a power law distribution.

Also worth noting that there's a sort of bimodal selection effect going on here -- it's unlikely that you use exactly 2k minutes/month, since you'd be hitting your limit and that would be disruptive. So the closer you get to using 2k minutes, the more likely you are to pay for more than the free tier. So I'd expect this pricing change to also force some users that were previously on 400 minutes +- 100 to have to upgrade too; this will impact some of the 98.5% of free users that are using <= 400 _on average_ per month.

Re: Gitlab reducing free tier CI/CD minutes from 2000 to 400 minutes

#162
post #94

Earlier quoted context omitted.

There is a global recession out there, of the kind that only happens once every 3 or 4 decades. Even if those companies aren't losing revenue (they probably are), there is less investment money too, so they are still impacted.

it isnt evenly distributed. usage of cloud services is UP if aws results are any indication. gitlab should experience a similar lift.

Investment money drying up is very well distributed. Even if none of those companies are looking for money right now, when it gets tight it's a good practice to reduce your spending so you need less of it.

Those things the OP is talking about are all investment, so it's natural that they get cut.

Re: Gitlab reducing free tier CI/CD minutes from 2000 to 400 minutes

#163
post #45

Earlier quoted context omitted.

I mean like other public cloud providers it would make sense to have instances and per minute pricing for an instance. If there is only one instance type that's fine.

What about if there's one instance type, but sometimes that instance gets upgraded so that the same things take less time? Is there a unit that would make more sense than "minutes", and be stable over time? For instance, "time to compile XYZ well-known project"?

Time to compile is a hard to gauge metric. I’d rather just be transparent that the instance type has changed.

It’s presumably in a big standardized DC. They don’t have a continuum of instance configurations, they probably upgrade rarely and systematically. If they are mid upgrade just have 2 instance types available then sunset the older one. Since the upgraded instance is a new instance type it can have new (or same) pricing. In addition, they could publish benchmarks for each instance type if they want.

It is literally what we see with cloud providers having v1/v2/v3 names for some instance types.

Re: Gitlab reducing free tier CI/CD minutes from 2000 to 400 minutes

#164
post #155

Earlier quoted context omitted.

I love Sourcehut, but Sourcehut's only competitive right now in the indie/free software enthusiast market. I doubt Gitlab views them as a major threat.

That is what GitHub thought about Gitlab

It's not the best comparison. Gitlab is VC-backed, whereas Sourcehut aims for slow, sustainable growth. Plus, the UX decisions of Sourcehut are so drastically different from Gitlab/Github that it doesn't threaten existing customers very much.

Re: Gitlab reducing free tier CI/CD minutes from 2000 to 400 minutes

#165
post #39

For smaller projects who aren't ready to start spending yet, it's pretty trivial to spin up your own runners on a server. Not sure how it scales, but Gitlab has pretty solid guides on how to make one. It took me maybe an hour the last time I looked at it, worth checking out. Definitely easier to drop $10 than maintain that though, I'm a fan of Gitlab's CI/CD infrastructure.

This thing of spending like an hour setting up a runner is one of the things I wanted to address with https://boxci.dev - A CI service I’ve built with a similar bring your own runners model but where “setting up the runner” consists of just installing a package, literally done in seconds :-) You should check it out.

To be fair, setting up a runner for Gitlab CI is very simple too. We self-host GitLab and we only have one runner on duty, but some projects have many stages that can be executed in parallel. I start a docker runner on my laptop before pushing new commits, which cuts the CI wait time by half.

Re: Gitlab reducing free tier CI/CD minutes from 2000 to 400 minutes

#166
Can anybody provide more info about how to set up your own runners? I have a VPS which runs dokku - can I spin up some containers there? Or can I just run it locally on my laptop (usually my laptop is connected to the internet when I push my changes and trigger CI so it could run there?)

edit: I had the look at the docs but they're quite overwhelming with lots of options. I run linux on my laptop. If the setup is too complicated I'll just purchase some minutes and call it a day

Re: Gitlab reducing free tier CI/CD minutes from 2000 to 400 minutes

#168
post #4

$4/mo for 2000 minutes is reasonable. GitHub Actions does 2000 minutes for free/3000 minutes for $4, wonder if they'll drop their free tier a bit without the competition.

At $4/month you can get a server from anyone for 700+ hours of CICD .. this doesn't sound like a great deal to me unless you're CICD can't exist without ~2gb/ram and the cpu limits... Or unless GitLab runners have 16+GB RAM and lots of CPU for large jobs

Today, for our Linux Runners on GitLab.com, those Runners are currently offered only on one machine type, Google Compute n1-standard-1 instances with 3.75GB of RAM. Our current Windows Runners on GitLab.com are Google Compute n1-standard-2 instances with 2 vCPUs and 7.5GB RAM. In the future, for Linux and Windows Runners, we will offer more GCP machine types. For our soon to launch macOS Build Cloud beta, we are planning to start with one virtual machine size and then possibly offer different machine configurations at GA.

So as you get going initially with GitLab SaaS, you don't have to set up your Runners for your first CI/CD jobs. Then, depending on your requirements, and as your use cases evolve, you can easily set up your own Runners but still benefit from the included minutes.

Darren Eastman - Product Manager GitLab Runner

Re: Gitlab reducing free tier CI/CD minutes from 2000 to 400 minutes

#169
post #136

Why many words when little would do? “We want to reduce cost and make more money, therefore today we reduce the number of free minutes from 2000 to 400 for free accounts. There are options to buy more minutes. kthxbye.” So tired of corporate PR BS.

Sure, and let's let the marketers make any changes they want directly to the master branch.
Post reply on HN