Setting up goreleaser to handle releases #474
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
To date releases have been a sort of manual process. The docker image was pushed on tagged releases, but then I needed to create the release in GH, copy all of the entries from CHANGELOG.md to it and finally build the binaries and attach them to the release. [GoReleaser](https://goreleaser.com/) can take care of all of that. When a tag is created, it will push the docker images and create the GitHub release with all of the CHANGELOG details (from the commits) as well as all of the binaries for supported OSs and archs. Brilliant! I also cleaned up the Makefile a bit to make things easier and avoid the need for installing binaries into system folders. With the exception of docker and unzip, everything else will be installed in `./bin` locally as needed. See `make help` for all the options.
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.
To date releases have been a sort of manual process. The docker image
was pushed on tagged releases, but then I needed to create the release
in GH, copy all of the entries from CHANGELOG.md to it and finally build
the binaries and attach them to the release.
GoReleaser can take care of all of that. When
a tag is created, it will push the docker images and create the GitHub
release with all of the CHANGELOG details (from the commits) as well as
all of the binaries for supported OSs and archs. Brilliant!
I also cleaned up the Makefile a bit to make things easier and avoid the
need for installing binaries into system folders. With the exception of
docker and unzip, everything else will be installed in
./binlocallyas needed. See
make helpfor all the options.