Migrate CI to GitHub Actions as Travis CI is ending their free OSS builds #738
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Credits where its due: I borrowed the PR title from dask/community#107 |
|
Merging, local tests on macOS aren't that high of a priority. |
888520ll19811209ll
approved these changes
Jan 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following Travis CI's recent OSS announcement, the decision has been made to move the CI to GitHub Actions. This PR takes care of that. Thanks to @kmarilleau for contributing most of the new code and changes.
Background : Travis CI announced on November 2, 2020 that they were changing their pricing model.
The consequences for opens source projects are:
For reference, one full run (two jobs, one for two containers setup, the other for three containers setup) of this project's tests currently consume about 25 minutes of run time on Travis CI. We're already down to 263 minutes since the pricing model change took effect.
Travis CI claim that "an allotment of OSS minutes will be reviewed and allocated on a case by case basis" upon application. Such an application was made about one month ago. I haven't received any answer to date.
GitHub Actions seems to works pretty well and faster than Travis CI did without any run time limitation (yet).
The only, somewhat substantial "but" is that
jwilder/docker-gendoes not work properly on GitHub Actions runners. I've forked the upstream repository and made a patched branch that is being used to build patchednginx-proxy/nginx-proxyandjwilder/docker-gencontainers that work on GitHub Actions. Appart from the patcheddocker-gen, they're identical to their upstream counterpart.I still have to check local testing on Linux and MacOS, and will merge this once it's done next week.