Migrate build to Travis CI .com (from .org)

[ilons]

In order for us to continue being able to build the project, we should as soon as possible migrate from travis-ci.org to travis-ci.com, as the .org service will be switched into read-only archive by new year.

Currently, this "only" affect us in that our builds take hours to get scheduled due to the huge job queue that builds up on travis-ci.org, as they move infrastructure away from .org.

More information about the migration (and instructions) can be found here: https://docs.travis-ci.com/user/migrate/open-source-repository-migration

[ilons]

Looking at the build queue on https://www.traviscistatus.com/, it's an ugly build-up for open source projects.

[ilons]

Further reading, encountered this little curve ball: https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing "For those of you who have been building on public repositories (on travis-ci.com, with no paid subscription), we will upgrade you to our trial (free) plan with a 10K credit allotment (which allows around 1000 minutes in a Linux environment)."

[ilons]

Might be worth having a look at Github Actions as a replacement (example). I think it's still worth migrating to travis-ci.com (and applying for more credits) as a first step tho.

[mjuenema]

Bastards (excuse the Australian expression)!!! It appears that the new owners want to kill Travis-CI. Let's investigate alternatives, e.g.

• Github
• CircleCI
• Gitlab
• others?

We could use the free trial Travis-CI minutes in the meantime, so not to interrupt any work towards the 0.9 release.

[ilons]

I think using the free credits on travis-ci.com is a good start, while looking for alternatives. Having to apply for new credits continously is hardly an appealing option.

[mjuenema]

I started investigating Github Actions. See the .github/workflows folder in the github_actions branch and Actions in the menu at the top.