-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish The Binary to various package management systems #7
Comments
we can also explore
|
we can utilize goreleaser. |
Didn't know about goreleaser. but will look into it. |
Both GoReleaser and JReleaser work in similar ways. However, the funtamental difference between these tools is that GoReleaser has tight integration with the Go build tool chain (it can build and release binaries) while JReleaser does not build binaries (it might assemble archives though) and expects target binaries to be given as inputs. Both tools offer similar features (there's a large intersection) while at the same time provide unique features. |
Check out the PR, I added goreleaser support. |
⚪ homebrew - Homebrew/homebrew-core#165860 |
FWIW Releasing Go projects with JReleaser just became easier thanks to the recently added |
As a user, I would rather not download the source code, compile to have binary.
A common practice for downloading and installing CLI tools is the use of popular Package Manager like Chocolatey on Win or Homebrew on Mac and so on.
One way to accomplish is to create a pipeline for each package manager.
Another alternative to have an all-in-one solution is to use https://jreleaser.org/ that provides many option to release and publish the binary to many package management systems. see full list https://jreleaser.org/guide/latest/integrations.html#_package_publish
At least we should support the following option
The text was updated successfully, but these errors were encountered: