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

#1

Post by kraf » Thu, Sep 03, 2020, 12:38 PM UTC

Gitlab reducing free tier CI/CD minutes from 2000 to 400 minutes
about.gitlab.com

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

#2

Post by immago » Thu, Sep 03, 2020, 4:38 PM UTC

Honestly not that big of a deal given that(I would assume) most probably run their own gitlab runners. I personally use the free tier and have a bunch of my own runners.

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

#3

Post by bovermyer » Thu, Sep 03, 2020, 4:49 PM UTC

This seems totally reasonable.

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

#4

Post by avolcano » Thu, Sep 03, 2020, 4:51 PM UTC

$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.

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

#5

Post by sushshshsh » Thu, Sep 03, 2020, 4:55 PM UTC

Metering of services like this only makes sense for organizations that don't have the time or expertise or desire to maintain the open source, self-hosted version themselves.

Raspi and similar devices will some day hopefully rid the world of this tyranny of having to trust a website like this and pay them for eternity and hope they dont go down and hope they dont raise prices (oops) and hope they dont obfuscate pricing like ermmm well every cloud provider has.

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

#6

Post by sam0x17 » Thu, Sep 03, 2020, 4:57 PM UTC

They sort of hang themselves with this -- gitlab runners will occasionally hang and just run for the full 1 hour max, making it very easy to max out your hours. Presumably they don't fix this so people max out their hours and have to buy more, but it also hurts the bottom line of their free tier. I see this happen at least 2x a month on our project, and it doesn't seem to correspond with any particular docker image.

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

#7

Post by atonse » Thu, Sep 03, 2020, 5:08 PM UTC

Seems like they’ve done it in a pretty reasonable way.

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

#8

Post by [deleted] » Thu, Sep 03, 2020, 5:10 PM UTC

sam0x17 wrote: post #6

They sort of hang themselves with this -- gitlab runners will occasionally hang and just run for the full 1 hour max, making it very easy to max out your hours. Presumably they don't fix this so people max out their hours and have to buy more, but it also hurts the bottom line of their free tier. I see this happen at least 2x a month on our project, and it doesn't seem to correspond with any particular docker image.

[deleted]

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

#9

Post by pkaye » Thu, Sep 03, 2020, 5:10 PM UTC

sushshshsh wrote: post #5

Metering of services like this only makes sense for organizations that don't have the time or expertise or desire to maintain the open source, self-hosted version themselves. Raspi and similar devices will some day hopefully rid the world of this tyranny of having to trust a website like this and pay them for eternity and hope they dont go down and hope they dont raise prices (oops) and hope they dont obfuscate prici…

It seems you can already use your own runners.

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

#10

Post by cpb » Thu, Sep 03, 2020, 5:18 PM UTC

sam0x17 wrote: post #6

They sort of hang themselves with this -- gitlab runners will occasionally hang and just run for the full 1 hour max, making it very easy to max out your hours. Presumably they don't fix this so people max out their hours and have to buy more, but it also hurts the bottom line of their free tier. I see this happen at least 2x a month on our project, and it doesn't seem to correspond with any particular docker image.

Can you reproduce this behaviour in local runners?