ci: Build and publish release binaries from CI#2
Merged
Conversation
Pushing a v* tag builds static linux amd64 and arm64 binaries and creates the GitHub release with the goofys, goofys-amd64, and goofys-arm64 assets that image builds download from releases/latest. Pull requests build the tree and run the unit tests. Claude-Session: https://claude.ai/code/session_0191kNQ9ZxzwEng9QfcfBKe6
giraffesyo
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What does this PR do?
Adds GitHub Actions workflows to the fork:
release.yml: pushing av*tag builds static (CGO_ENABLED=0) linux amd64 + arm64 binaries and creates the GitHub release with exactly the assets past releases carried and image builds consume fromreleases/latest/download/:goofys(copy of amd64),goofys-amd64,goofys-arm64.ci.yml: PRs and master pushes get a linux build of the whole tree plus theapi/...unit tests.Why
Releases (v0.24.0 and earlier) were built and uploaded manually. With the SAS-token change (#1) needing a release cut for the ACTIVATE Azure mount work (parallelworks/core#17025), automating the release path removes the manual build and makes future fork releases one
git tagaway.Testing
Same build commands verified locally:
CGO_ENABLED=0 GOOS=linux GOARCH={amd64,arm64} go build .from the repo root (package main is at the root), andgo test ./api/...passes.https://claude.ai/code/session_0191kNQ9ZxzwEng9QfcfBKe6