multi-build/multibuild

Is there a plan to migrate to travis-ci.com ?

mattip opened this issue · 5 comments

travisci.org, where the CI is currently run, is shutting down. Is there a migration plan for this repo?

I had the impression from the message at the top of the travis-ci.org site, that the accounts would be automatically migrated - is that not true?

From https://docs.travis-ci.com/user/migrate/open-source-repository-migration, the .org location will continue to exist as read-only, so at least the links to Travis should be updated for the new location.

The bigger concern might be about travis-ci.com forcing paid plans - https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing#building-on-a-public-repositories-only

It would be easy enough to migrate the yml file to another provider, but as far as I know only travis offers ppc64 and s390x hardware. circleci, azure, and github actions only support x86 hardware. So migrating would mean splitting CI between different vendors.

A recommendation from another discussion - python-pillow/Pillow#5028 (comment)

See dbhi/qus. It was created and it is used precisely for migrating ARM, PPC64 and S390X jobs to GHA.

I think this can be closed, the repo was migrated to travis-ci.com