New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Travis and Cirrus, use GH also for FreeBSD #1880
Merged
Merged
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
giampaolo
changed the title
Get rid of Travis and Cirrus
Remove Travis and Cirrus, use GH also for FreeBSD
Nov 15, 2020
@giampaolo just FYI Cirrus CI is still free and was free at the time of this PR. We don't have any monthly limits on CPU minutes used as you might imply. |
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.
Get rid of Travis (yes, after so many years) and Cirrus services for CI testing. Reason: both of them are no longer free for public repos (require payment). From now on, GitHub actions will take care of CI testing and will generate wheels on:
It turns out it is possible to run FreeBSD on GitHub Actions by making it run macOS and virtualize FreeBSD on top of it.
AppVeyor will take care of Windows (tests + wheels). Also GitHub Actions is able to do that (I left the commented code in place), but it takes around 18 mins to complete. AppVeyor is also relatively slow, but this way we split the load and keep Linux/macOS/FreeBSD builds faster and more agile when pushing changes.
Related to #1879.