Intending to use Travis for a FOSS project? - Forget it!

[SlySven]

The front page of the travis.com site includes:

And there is the following announcement here:

Open Source at Travis CI - An Update

We’ve recently had a lot of feedback and questions from the Travis CI community and beyond about the future of open source at Travis CI, following our recent announcement about how we are tackling accounts that are taking valuable resources away from your builds. Open source has always been and always will be at the core of what Travis CI stands for, reflected in the fact that we’re still committed to offering accounts specifically for open source repositories. We’re also partnering with lea…

However - they are now lying through their teeth - they do not want anything to do with projects that do not give them money.

For examples, see:

Open source plans

If it helps, I have published a Github Action that is creating the build-script from .travis.yml (ported from the original travis-build) and runs it. As I was running into the same kind of problem after migrating from travis-ci.org to travis.ci.com recently (support told me I should do so and while doing credits already ran out within less than three days): The action allows to keep the same build script process across Travis and Github (as you know integration I guess this is an overstatemen…

OSS only credits request processing time estimate?

OSS credits are on hold indefinitely looks like. [screenshot]

Build delays for open source project

As was pointed out in Builds hang in queued state - #6 by Montana linked to earlier in this topic, Travis is moving workers from travis-ci.org to travis-ci.com in preparation to fully close .org (or rather, make it read-only) around the New Year. So you need to migrate to .com to stop experiencing delays. Note the caveats:

.org -> .com migration unexpectedly comes with a plan change for OSS. What exactly is the new deal?

Oh hey though. I just realized, it turns out that open source will no longer be offered free service on travis-ci.com either. In case some of you had missed the announcement. I had realized my builds stopped working on .org [1] , and was moving them all over to .com – where they started working as expected again – but I hadn’t realized that was just buying me a tiny bit of time. It looks like legacy open source accounts on .com will get a certain number of hours credit, and after those are…

Concurrency for open source projects

Travis told me on Twitter: Hi there! Just to clarify, you’ll continue on getting 5 concurrent builds when moving across open source repos to https://travis-ci.com - this was something we overlooked when moving domains (rather than anything to do with the acquisition), but has been fixed now!

They seem to offer some free credits - but those are not replenishable and since it does not seem to be possible to make contact with a human at Travis to arrange “OSS Credits” once they run out your FOSS project will be screwed.

For several years Travis had been the go to platform for CI for a multi-plaform FOSS project - but since Idera stepped it it seems that they are just squeezing Travis’s assets (and the paying commercial customers) until there will just be an empty husk left…

A FOSS project coder that has now switched from Travis to a workable platform.