logoalt Hacker News

olafmollast Tuesday at 9:45 PM1 replyview on HN

CircleCI does only charge for self-hosted runners generated egress and/or artifact storage:

"Any Network Egress to CircleCI will be charged. At this current time, this includes CircleCI Caches, Workspaces, and Artifacts and will be charged at the normal rate according to your Usage Controls.

The only network traffic that will result in billing is accrued through restoring caches and workspaces, and downloading artifacts to self-hosted runners. Retention of artifacts, workspace, and cache objects will result in billing for storage usage.

Since your builds will not be running on CircleCI's Infrastructure, you will not be charged compute credits"

https://support.circleci.com/hc/en-us/articles/2064321965685...

I think that's fair. In my personal opinion most people started using GitHub Actions because it “came for free with the VCS and/or our MS contract” and it was “good enough for the job”. Now might be a good time to look around at the alternatives again. There is a reason that f.e. CircleCI is doing fully focused CI/CD for 10+ years and is still going strong. Plenty of businesses don’t want to put all their eggs in one (MS) basket, for all kinds of reasons. I guess today one of these reasons became obvious.

Disclaimer: I work at CircleCI.


Replies

bencedyesterday at 1:17 AM

CircleCI charges for concurrent job runs (which include self-hosted runs), no? They (you, I guess) obfuscate that by saying you get "Unlimited" if you take the "Talk to sales" route but that's not the same as not charging.

show 2 replies