08 Dec 2020 software
Travis CI recently announced a new pricing model. Most prominently, open-source builds are no longer free. Instead, they’re giving current open-source maintainers 10,000 credits to start - about 1,000 minutes of Linux build time - and selling additional credits at a rate of 25,000 credits for $15.
As expected, HackerNews was upset, primarily because Travis CI explicitly stated that open-source builds would be free forever. Nothing stings quite like the ol’ bait-and-switch.
Not all hope was lost, however. Buried in the announcement:
We will be offering an allotment of OSS minutes that will be reviewed and allocated on a case by case basis. Should you want to apply for these credits please open a request with Travis CI support stating that you’d like to be considered for the OSS allotment.
Mostly just to exhaust my options, I opened a request:
Hi! I maintain a public repository on GitHub called spotify-playlist-archive. As the name suggests, it’s a community-curated archive of public Spotify playlists. May I sign up for an Travis CI open source plan, so that the project continues to run smoothly? Thanks, Mack
About a week later, I got a reply:
Hello Mack, Thanks for your patience while we worked on your request. We are awaiting further approval for your account and will promptly apply credits as directed to your account. In the meantime, however, we have added 50,000 credits to your account to enable you continue using the service. I hope this helps. Thanks and we will follow up soon.
To their credit, I actually did get the 50,000 credits - about 83 hours and 20 minutes of build time - which is enough to last me years since I only use a minute of build time per day. Still, it’s been almost two weeks since that reply, and I have a feeling they’re not actually going to follow up, especially given that HackerNews says they’re no longer giving credits to open-source projects. Only time will tell…
27 Mar 2021
Travis CI never got back to me, so today I migrated all (two) of my repositories to GitHub Actions. The migration was actually pretty simple:
.travis.yml config fileHere’s an example commit: https://github.com/mackorone/spotify-playlist-publisher/commit/a6541aa86fd5ca65a13e24ce439cd7c060888fce
And to really put the nail in the coffin, I also:
So long, Travis CI, and thanks for all the fish.