The new pricing model for Travis CI
blog.travis-ci.com
The new pricing model for Travis CI
1–10 of 88 posts
Re: The new pricing model for Travis CI
#2i 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
Re: The new pricing model for Travis CI
#3i 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
You can legally only run macOS on apple hardware, and that's expensive.
Re: The new pricing model for Travis CI
#4i 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
Building Mac build farms is way more of a pain and absolutely costs more. There are a few services dedicated to making it easier, but Apple isn’t trying hard to make people’s lives easy in this.
Re: The new pricing model for Travis CI
#5The 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.
Re: The new pricing model for Travis CI
#6i 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.
Re: The new pricing model for Travis CI
#7i 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
You can legally only run macOS on apple hardware, and that's expensive.
Also, there's a lack of dedicated server products.
Re: The new pricing model for Travis CI
#8I 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 pay per byte transferred and CPU instruction executed -- if they make the hardware or network faster, the price stays the same, but they can do more work with their infrastructure. And if you schedule less work, the price for you goes down.
But, it's simply not done, and that's kind of sad because slow CI is probably the biggest engineering time killer in existence. Other than Hacker News ;)
Re: The new pricing model for Travis CI
#9Earlier quoted context omitted.
You can legally only run macOS on apple hardware, and that's expensive.
Also, there's a lack of dedicated server products.
I loved how imgix solved this: https://photos.imgix.com/racking-mac-pros (definitely not cheap, but super slick)
Re: The new pricing model for Travis CI
#10Earlier quoted context omitted.
Also, there's a lack of dedicated server products.
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")?