This repository currently has a .travis.yml file that triggers Travis CI builds for e.g. pull requests. On Dec 16, 2021, the Eiffel Technical Committee decided that existing uses of Travis CI should be migrated to GitHub Actions (see minutes).
Motivation
Nowadays Travis CI isn't as free to use as it used to be. There's a limited number of credits given to each organization, and right now we're fairly close to the limit. In recent years GitHub Actions has been introduced and it should be adequate for most use cases.
Benefits
Decreased risk of service interruptions if we reach the usage limit (and nobody will have to spend time on requesting increases in the limit).
Possible Drawbacks
Probably none, unless your current .travis.yml contains steps that are very difficult to replicate in a GitHub Actions workflow.
Description
This repository currently has a .travis.yml file that triggers Travis CI builds for e.g. pull requests. On Dec 16, 2021, the Eiffel Technical Committee decided that existing uses of Travis CI should be migrated to GitHub Actions (see minutes).
Motivation
Nowadays Travis CI isn't as free to use as it used to be. There's a limited number of credits given to each organization, and right now we're fairly close to the limit. In recent years GitHub Actions has been introduced and it should be adequate for most use cases.
Benefits
Decreased risk of service interruptions if we reach the usage limit (and nobody will have to spend time on requesting increases in the limit).
Possible Drawbacks
Probably none, unless your current .travis.yml contains steps that are very difficult to replicate in a GitHub Actions workflow.