PoC: Add GitHub actions workflow #152
Draft
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
rgl
force-pushed
the
github-actions
branch
3 times, most recently
from
1a24139 to
65ccff5
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.
This adds a GitHub actions workflow to build the binary and release it as a GitHub Release.
As an example, I did a workflow run at https://github.com/rgl/dockutil/actions and a GitHub Release at https://github.com/rgl/dockutil/releases (where you can also see the tarballs with the binaries).
This is currently a PoC and it only supports the x86_64 architecture. But if this change is welcomed, I will, with your help, expand it to also build for the arm64 architecture and release the binaries as two different tar balls.This now builds x86_64 and arm64 binaries and packages them inside a tarball.The only thing missing is the applying the version. Maybe the version could come from the git repository tag. Let me known what you think.
Please note that is currently based on the #131, which I think, should also be merged; once that happens I'll rebase this PR over it.