Automate release process and binary builds #343
Labels
contributor experience
Quality-of-life improvements or changes to project contribution processes or resources
new change
Adds new capabilities or functionality
research
Research and more data is needed to make a decision
Milestone
Discussed in 2020-10-11 meeting.
Summary
Automate the creation of multi-OS, multi-arch binaries of TeleIRC releases
Background
Is your feature request related to a problem? Please describe:
When we release TeleIRC, the person cutting the release manually builds the Go binary and uploads it to GitHub. This is OK, but an end-user who is not using the same OS and architecture as the person cutting a release must build their own binary. Unwieldy for the average person!
Describe the solution you'd like:
Automatically build binaries for the most common architectures and operating systems.
Details
We checked out fellow Go project Matterbridge to see how they do it. Matterbridge releases include countless binaries for multiple operating systems and different architectures. It appears they have some automation for this, but it is unclear how it works:
.goreleaser.yml
.github/workflows/development.yml
GitHub workflowOutcome
Make TeleIRC binaries available to end-users on a variety of platforms without making end-users manually build/compile TeleIRC
The text was updated successfully, but these errors were encountered: