Live data from Hacker News

Pricing Changes for GitHub Actions

resources.github.com

551–560 of 853 posts

Re: Pricing Changes for GitHub Actions

#551

Earlier quoted context omitted.

no, I'd cut the monthly seat cost and grow my user base to include more low-volume devs but realistically, publishing a web page is practically free. you could be sending 100x as much data and I would still be laughing all the way to the bank

Publishing the page is only the last step. It's orchestrating the stuff THEN publishing it. If you think that's easy, do it for me. I have some projects to migrate, give me the link of your service.

There are several services I know who offer this for free for open source software, and I really doubt any commercial offerings of that software would charge you extra for what is basic API usage.

Re: Pricing Changes for GitHub Actions

#552

Earlier quoted context omitted.

Your pricing page seems to have changed intra-day. but now it's about $400ish. 30 users + 500 builds. However I don't know what counts as a build, since a typical commit to an open PR uses 10 GH runner machines simultaneously doing odd jobs like integration tests, releases, deploys, etc...

Can you send a link to the page you’re looking at? Thanks! Pricing should mostly just be users + build minutes (for cloud runners) + storage. There is a few other optional, feature specific costs. Self hosted runners are free, but you need to self host caches/workspaces - our native ones have an egress bill to self hosted runners.

https://circleci.com/pricing/build-your-plan/

If self-hosted runners are free that would change our equation a bit. I'll talk to some folks here, I liked using this product at another company I worked at - but this would most likely shake out AFTER Github charges us the first time.

Re: Pricing Changes for GitHub Actions

#553

I really enjoy how they list the price PER MINUTE to make it sound like this isn't absurdly expensive. A lot of people leave their self-hosted runners running 24/7 because, after all, they're self-hosted. This is $2.88/day, $86.4/month, $1051.2/year. For them to do essentially nothing. Most notably, this is the same price as their hosted "Linux 1-core" on a per-minute basis. Meaning they're charging you the same for…

You can get far bigger VM for that per month. It's ridiculus. Of course entirely expected after MS buyout, if anything I'm surprised it took that long

Yup. Took wayyy longer than I actually expected as well. But the change of top management and closer integration with the whole MS behemoth is likely to make those kind of things accelerate now

Re: Pricing Changes for GitHub Actions

#554

Earlier quoted context omitted.

As long as they're reserving resources for your job during the period of execution, it does.

Charging people to maintain a row in a database by the minute is top-tier, I agree.

If you really think that's all it is, I would encourage you to write your own.

Re: Pricing Changes for GitHub Actions

#555

Earlier quoted context omitted.

Charging people to maintain a row in a database by the minute is top-tier, I agree.

If you really think that's all it is, I would encourage you to write your own.

It would be silly to write a new one today. Plenty of open source + indy options to invest into instead.

For scheduled work, cron + a log sink is fine, and for pull request CI there's plenty of alternatives that don't charge by the minute to use your own hardware. The irony here, unfortunately, is that the latter requires I move entirely off of GitHub now.

Re: Pricing Changes for GitHub Actions

#556
post #475

Earlier quoted context omitted.

GitHub Actions runners are hard to self-host. The runner configuration and registration process is unnecessarily byzantine. [1] They can't cancel jobs cleanly. [2] There are consistency problems everywhere. [3] Their own documentations describes horrible things unless you use runners in JIT mode. Though JIT runners are not always removed after exit. If there is a worse self-hosted CI runner, I haven't yet met it. [1]…

I am developing a self-hosted solution for this [1]. It’s true that it’s somewhat of a pain but JIT runners allow a lot of flexibility that we don’t find elsewhere. [1] https://runs-on.com

I did something very similar.

Create/start/stop/terminate EC2.

https://github.com/redoapp/fast-actions-runner-ec2

Re: Pricing Changes for GitHub Actions

#557

It is us, developers, who convinced our management to purchase GitHub Enterprise to be our forge. We didn't pay any heed to the values of software freedom. A closed source, proprietary software had good features. We saw that and convinced our management to purchase it. Never mind what cost it would impose in the future when the good software gets bad owners. Never mind that there were alternatives that were inferior…

Have any suggestions to those community-developed and maintained options?

Gitea. Gitlab (ish?).

Re: Pricing Changes for GitHub Actions

#558
post #546

I really enjoy how they list the price PER MINUTE to make it sound like this isn't absurdly expensive. A lot of people leave their self-hosted runners running 24/7 because, after all, they're self-hosted. This is $2.88/day, $86.4/month, $1051.2/year. For them to do essentially nothing. Most notably, this is the same price as their hosted "Linux 1-core" on a per-minute basis. Meaning they're charging you the same for…

How can they charge for something self hosted per minute? Thats very weird to me. If I run the software I should pay a single time only, if I don't own it then why self-host im the first place? Maybe this is designed to scare people away from self-hosting altogether?

I do believe, this is to disincentivize self-hosting for smaller-medium workloads. In essence, they're saying that if you're small, you should just use their Linux 1-Core, but if you're medium-to-large you won't care about the high cost.

It is a way of increasing lock-in for smaller-medium clients, without driving away their medium-large ones.

Re: Pricing Changes for GitHub Actions

#559
post #488

Earlier quoted context omitted.

It is duration of runs. He was just highlighting the absurde cost if you were to run it 24/7 like some people with their own self hosted runners do.

I am not understanding something. If its the price of runs, then its not always running. If its price of the agent to exist, then thats not paying per runs- then you’re right that people tend to leave their runners online 24/7- but I’ve never worked anywhere that had workers building 24/7.

We're targeting 4x different deployment pipelines, so while we aren't running 24/7, we are running the same number of hours but split over all our runners. Often runs are queued during our busy 8-hour work-day, and then unused for 16-hours.

Either way, we will likely pay 8-hours4-pipelines5-days=160 hours per week, just shy of 168-hours for true 24/7. This currently costs $0 just for context.

Re: Pricing Changes for GitHub Actions

#560

this is the third article about it, we know, good times are over, will start migrating towards something else

don’t lie you’ll just bitch and moan and keep using it anyway

the downvotes are from those who can’t cope with this truth
Post reply on HN