Move CI away from Travis #63
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
|
Also removing the recently-added NetBSD runner, waiting for SSH in CI scripts gets flaky. Oh well. |
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.
Travis only gives us a limited number of credits now, lovely. It's pretty easy to move the x64 Linux and Windows builds away from Travis to Github Actions, so do that.
Unclear if there's a good way to move the other architectures (aarch64, $SOMETHING_BIG_ENDIAN) off of Travis. Github Actions doesn't even allow KVM, while Cirrus does but has no special facilities for setting up qemu. (Lots of folks do slow cross-arch docker on Github Actions, but that won't let FUSE magically work.) Will keep thinking about this.