11–20 of 88 posts
Earlier quoted context omitted.
I loved how imgix solved this: https://photos.imgix.com/racking-mac-pros (definitely not cheap, but super slick)
Does that actually make sense, or is it just another Engineering team doubling down on their poor early architectural choices ("or lack thereof")?
(GitLab supports using its CI/CD on a non-GitLab repo just fine, but it can cause some initial confusion.)
I guess this is the same pricing model as CircleCI? I've always found "build minutes" to be a little bit of a vendor-favored pricing model. I really love wanting to do a release, and watching my CI provider take three minutes to pull down a 30MB docker image, or "npm install" running at dialup speeds. All while they're billing you per minute -- they make money by not investing in their infrastructure! I'd prefer to p…
I got our CI pipeline from 90 minutes to 10 minutes by running parts in parallel and applying lots more hardware.
The cost is essentially nothing ($0.10 / build) compared to the time developers spend waiting.
I currently use & recommend buildkite because they offer a preconfigured cloudflare template that does all of the hard parts for you.
The interesting part is the FOSS changes Basically they significantly cut the FOSS usage by instead offering free credit and then reviewing the projects on case-by-case basis if you run out of it. It's a big change, but honestly, I don't know how they could they provide free computation for any public repo no questions asked as they have been up until now.
i wonder if there are actually higher costs associated with macOS, or if this is just segmentation based on the fact that macOS users are more willing to pay more for software
Travis CI and GitHub both use MacStadium's infrastructure for macOS builds, not their own. https://www.macstadium.com/customers/travis-ci
Based on MacStadium's public pricing, which is $150/month for the base model of the latest Mac Mini, this cannot be cheap for Travis, especially given they offered (past tense) Mac OS builds for free.
Not surprised to see them start charging more, but it's coming at exactly the wrong time given that GitHub (with Actions) is now offering a product that's a fair bit better, and it's still free.
It's 100% open source and there's almost no income (some github sponsors) for it. I guess welp we'll have to switch away, or have to constantly send "ask" tickets to get free credits :/
Many of us will be in this position.
The interesting part is the FOSS changes Basically they significantly cut the FOSS usage by instead offering free credit and then reviewing the projects on case-by-case basis if you run out of it. It's a big change, but honestly, I don't know how they could they provide free computation for any public repo no questions asked as they have been up until now.
I see a lot of mentions of "travis-ci.com" in this post, are the OSS changes meant to impact travis-ci.org as well, or just OSS projects that are using travis-ci.com for some reason?
Source: https://mailchi.mp/3d439eeb1098/travis-ciorg-is-moving-to-tr...