feat: Migrate travis CI to github actions, fixes #105 #132
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
dalehamel
changed the title
This moves the CI and release process to github actions from Travis
dalehamel
force-pushed
the
github-actions
branch
from
d6da490 to
aa1d3b1
Compare
Closed
fntlnz
approved these changes
Oct 26, 2020
|
Good job @dalehamel - this is very useful and better than what we had. |
|
I removed Fixmie from the list of requirements for merge in Branch protection rules (that app does not exist anymore). I wanted to add the new checks from here as required but they don't appear. I guess there's some caching and I'll check later
|
|
oh wait! The new ones are
|
|
Oh this wasn't quite ready to merge, I discovered a couple more things. I'll follow-up with another PR to correct those. |
This was referenced Oct 26, 2020
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.
This moves the CI and release process to github actions from Travis for #105
To fully test this, I will need to either be made a full admin of the repo (@fntlnz @leodido are you able to do this?), or have an existing admin add the QUAY_TOKEN secret environment variable.
Here is a sample run: https://github.com/dalehamel/kubectl-trace/actions/runs/322349438
It uploads the dist folder for cross builds, as well as the linux binary that it builds as part of the test process.
I plan on testing the gorelease script when we cut 0.1.1 shortly