When a project has reached that stage when it’s a good idea to post binaries, new questions arise such as where should they be posted? How do you make it easier for users to install and discover binaries? Where should releases be shared? Most importantly, can it be automated? There are so many requirements and considerations depending on the distribution channels -- wouldn't it be great to have a tool to make it easier? We'll have a look at GoReleaser and JReleaser, two tools that provide answers to these questions and more. These tools may be used to create GiHub/GitLab/Gitea releases and publish binaries that can be consumed from different distribution channels such as Homebrew, Snap, Scoop, and more. Once published, the release cab be automatically announced on Twitter, Slack, Gitter, Discord, and other communication channels.
Andres is a Java/Groovy developer and a Java Champion with more than 2 decades of experience in software design and development. He has been involved in web and desktop application development since the early days of Java. Andres is a true believer in open source and has participated on popular projects like Groovy, Griffon, and DbUnit, as well as starting his own projects. Founding member of the Griffon framework and Hackergarten community event. Author of JReleaser. You can find him on twitter too as @aalmiray. He likes to spend time with his beloved wife, Ixchel, when not hacking around.