And there so many other services with generous offers for open source maintainers that I appreciate and try to support in any way I can (often financially, as far as I'm able). Looking in the gift horse's mouthĪs I said earlier, I am appreciative of the acceleration in my own growth and career that Travis CI enabled over the past decade. I don't have enough time in my day to send off emails every few requesting extra build credits so I can continue maintaining my open source projects. How many credits (build minutes) you’d like to request (should your run out of credits again you can repeat the process to request more or discuss a renewable amount) 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. We will be offering an allotment of OSS minutes that will be reviewed and allocated on a case by case basis. Those who, like me, finished migrating to in the past couple of weeks to get out of that backlog hell are now realizing that we are going to have to beg for extra build minutes after our 1000 'trial plan' build minutes run out: There are many other open source developers and projects out there still using, who either haven't found the time or motivation to migrate to (or elsewhere, ideally), as evidenced by this massive daily backlog of build jobs: Note that we're not yet caught up to the end of the timeline.
I ran out of credits before I even saw the new billing plan notice.
#Google photos app for mac github free#
2011: Travis CI is founded, offering free open source CI integration with GitHub repositories.
Now, to shed a little more light on where, precisely, things went from bad to worse, I put together this little timeline of Travis CI's most important moments in relation to open source builds: At one time it was showered with praise on Hacker News and elsewhere for its culture and ethos.īut as the years passed, other CI systems became much more popular, until late in 2018, GitHub dropped the bombshell that was GitHub Actions, and it seemed like the outlook for Travis CI went to: What went wrong with Travis CI?įrom the outset, Travis CI was built to integrate with GitHub repositories and offer free open source CI. But with the testing, I'm able to keep up with build failures induced by bit rot over the years and review PRs more easily. Without that testing, and the ability to run tests on a schedule, I would have abandoned most of these projects. And almost every single project I built got immediate integration with Travis CI. I have built projects for Raspberry Pi, PHP, Python, Drupal, Ansible, Kubernetes, macOS, iOS, Android, Docker, Arduino, and more. For almost a decade, Travis CI made it possible for me to build-and maintain, for years- hundreds of open source projects. I am not one to look a gift horse in the mouth. I just spent the past 6 hours migrating some of my open source projects from Travis CI to GitHub Actions, and I thought I'd pause for a bit (12 hours into this project, probably 15-20 more to go) to jot down a few thoughts.
0 kommentar(er)
