Live data from Hacker News

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

about.gitlab.com

131–140 of 176 posts

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

#131
post #115

Earlier quoted context omitted.

This is exactly it. 1.5% of users does not equal to 1.5% of CI/CD minutes. And such messaging isn't always dishonest. If you have 99 users using 100 minutes each and 1 user using 10 million minutes, setting the max limit to say 1000 is a net benefit for the system and its users, at the expense of the one outlier.

Yes, but in this case one user couldn't use 10 million minutes, they were already capped at 2000. Now they are capped at 400 instead. So that limits how extremely disproportionate the high percentile use could be. As I said, that 1.5% of users could have been using at most 1600 more minutes a month than the new max.

They can make infinite repos though!

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

#132
I wish they would make there merge request work like GitHub’s pull requests. I always miss the messaging when there are merge conflicts. Also would be nice to have something similar to status checks with the annotations support like GH.

Now I am going to see if they fixed the bug were copy to clipboard stopped working a few months ago. Why would I want some JSON blurb intrad of branch name when copying it ️

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

#133
post #115

Earlier quoted context omitted.

This is exactly it. 1.5% of users does not equal to 1.5% of CI/CD minutes. And such messaging isn't always dishonest. If you have 99 users using 100 minutes each and 1 user using 10 million minutes, setting the max limit to say 1000 is a net benefit for the system and its users, at the expense of the one outlier.

Yes, but in this case one user couldn't use 10 million minutes, they were already capped at 2000. Now they are capped at 400 instead. So that limits how extremely disproportionate the high percentile use could be. As I said, that 1.5% of users could have been using at most 1600 more minutes a month than the new max.

If the other 98.5% don't use any minutes, then it's an 80% reduction. That seems pretty good. We can't say more without real numbers though.

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

#134

Earlier quoted context omitted.

It’s because cost isn’t the issue. The change is designed to convince more free users to switch to a paid account.

OK. But they're saying the number of free users that would have to switch to a paid account is 1.5%, right? Which doesn't necessarily seem like enough to justify a disruptive change that might scare customers... but I don't really know I'm hardly an expert or have experience in this kind of business. You think it is, is your hypothesis?

If they have 100x the free users than paid users it would totally be worth it. It depends on the numbers.

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

#135

Earlier quoted context omitted.

This and that are different things though. Nitro is for individual accounts and provides features for you as a user, boost is for the server and provides features for every user of the server. Maxing out a server takes 30 boosts but the level 3 perks seem pretty… thin on the ground: - +100 emoji (from 150 to 200) - 384Kbps audio (from 256) - 100MB uploads (from 50) - custom URLs Only the third one is somewhat useful,…

#4 is huge, especially if you're running the Discord to promote something else like a Twitch channel or a game. Is it worth the cost? Probably not. But I'd put it above larger uploads in terms of importance, and my discords hit the upload limit pretty often.

All replies here are missing that multiple users can stack their boosts, so no single individual needs to be paying 100 bucks a month.

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

#137
post #22

I've never really understood "minutes" as a unit of build work. What kind of server are we talking about? What CPU? How much RAM? How fast is the storage access? Is my instance virtualized? And if so, do I have dedicated resources? I have a build that takes around 70 minutes on an 8-core i9 with 32 GB of RAM and M.2 SSDs. What does that translate into for Gitlab "minutes"?

Wouldn't Watt hours (or Joules) be a unit that more accurately represents the amount of work being done, and the cost of running the physical server?

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

#138

Hetzner VPS for $35, caprover and you can install many one click apps, plus there is gitlab ce and some CI/CDs...For just $35 a month...

You can get an AMD bare metal for that price:

https://www.hetzner.com/dedicated-rootserver/matrix-ax?count...

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

#139
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.

I work at a medium-ish enterprise and the comm team forbids engineering from sending out notices to customers without clearing past them. Not sure if it’s the same for Gitlab, but sounds like something similar...

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

#140
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
Post reply on HN