Travis-CI has both moved to a paid model for doing anything beyond a trial period, and made it difficult to transition from travis-ci.org to travis-ci.com. I no longer want Travis-CI for FLiT.
As requested by Ian in issue #312, we will move to GitHub Actions instead of Travis-CI. It has better integration, it's just as easy, it has better documentation, and they have a free plan that is generous to public repositories.
Details:
GitHub Action for running automated tests is implemented with .github/workflows/automated-tests.yml
triggered when pushed to branches devel, main, or master
triggered for any pull request
removed installing pyelftools since it is no longer a dependency
removed top-level make build, since it does nothing now
replaced badge on the top-level readme
added a way to manually trigger a build from the Actions tab on the web interface
environment is on the latest Ubuntu rather than an arbitrarily old and unsupported Ubuntu that Travis-CI was using.
other than that, it's identical to the travis-ci setup
Documentation:
Nothing. Travis-CI was not mentioned in the current documentation files, so nothing needs changing. It would be good to document our continuous integration system, but that is outside of the scope of this issue and this change.
One change was to replace the top-level README.md file status badge with an equivalent one from GitHub Actions. Once merged in, this will be manually triggered to initialize the current status.
Tests:
No tests were changed, but they were tested using the new CI environment, and are passing using ubuntu-latest
Fixes #312
Description:
Travis-CI has both moved to a paid model for doing anything beyond a trial period, and made it difficult to transition from travis-ci.org to travis-ci.com. I no longer want Travis-CI for FLiT.
As requested by Ian in issue #312, we will move to GitHub Actions instead of Travis-CI. It has better integration, it's just as easy, it has better documentation, and they have a free plan that is generous to public repositories.
Details:
Documentation:
Nothing. Travis-CI was not mentioned in the current documentation files, so nothing needs changing. It would be good to document our continuous integration system, but that is outside of the scope of this issue and this change.
One change was to replace the top-level README.md file status badge with an equivalent one from GitHub Actions. Once merged in, this will be manually triggered to initialize the current status.
Tests:
No tests were changed, but they were tested using the new CI environment, and are passing using ubuntu-latest