Repository navigation
ci: publish official release binaries - #438
Merged
Merged
Conversation
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.
Attach official, statically linked ndt-server binaries to every GitHub Release, so consumers such as the BYOS Debian package can download pinned builds instead of compiling from source. Same workflow shape as m-lab/jostler#62.
release-binariesworkflow: onrelease: published, buildsndt-serverandcmd/generate-schemasfor linux/amd64 withCGO_ENABLED=0 -trimpath -ldflags "-s -w"and the sameversion.Versionandprometheusx.GitShortCommitstamps as the container image, then uploadsndt-server_<tag>_linux_amd64andgenerate-schemas_<tag>_linux_amd64pluschecksums.txtto the release.workflow_dispatchwith ataginput attaches binaries to an existing release. Releases before the cgo removal (fix(bbr): remove cgo dependency, build statically with CGO_ENABLED=0 #436) do not build withCGO_ENABLED=0, so the first release with binaries is the next one.This change is