Replace travis with GitHub actions #47
Open
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
Travis CI has gotten worse over the years with hour long wait times for builds, this is not acceptable especially with such a great alternative as github actions.
linkvt
force-pushed
the
replace-travis-with-github-actions
branch
from
e522f55 to
b51be4c
Compare
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.
Hi,
I did this mostly for learning about github actions but think it benefits the project as I noticed that Travis CI builds took extremely long until a build was scheduled.
Besides that docker buildx is now (since 20.10) out of experimental and eases the cross platform CI build.
Github actions is pretty simple to read and understand and has already many integrations, e.g. for cross plattform builds.
To get this build running you have to set three secrets in the github repo settings: https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets
All branches are build but only
stable(from themasterbranch) anddevelopare pushed to docker hub, if you have any suggestions I can implement them.BR, Vincent