Make Go binaries available as GitHub Release

[stormc]

Feedback Type

New enhancement request

Feedback

All the Go binaries should in addition to the manual installation method be available as GitHub Releases (https://github.com/margo/sandbox/releases) which enables packaging them properly in, e.g., ISAR or Yocto. Currently, we have to manually install the sandbox (e.g., device-agent) somewhere, extract the relevant Go binary, and place it into the image build toolchain which is error prone and could be easily avoided by having a GitHub Release that can simply be integrated into the respective image building workflows.

CC: @Silvanoc , @dennislickay

[vireshnavalli]

@singhmj-1 could you please check this

[stormc]

Thanks for picking it up. I assume you do this for x86_64 as well as for ARM64? Haven't seen a comment on this...

[singhmj-1]

Hi @stormc , we are discussing about the following artifacts to be part of every release:

1. Binaries : <name>-<version>-<os-platform>-<arch>
   a. linux-x86_64
   b. linux-arm64
   c. Any other platform or arch to be supported?
2. Container Images (should these be signed ones?)
3. Helm chart
4. Release Notes
5. Source code
   Any feedback from your side would be helpful. Thanks!

[stormc]

Ad 1. Linux x86_64 and arm64 is fine for now I think.
Ad 2. As the containers are carrying the Go binaries and not much more as of now, I would consider this secondary.
Ad 3. Kind of related to 2., but I would call this secondary as well. Once containers carry more, publishing containers makes sense.
Ad 4. This can be generated from the commits if you follow, e.g., conventional commits. Would be nice but without manual work if you take on this.
Ad 5. The Source Code should be tagged for each Release / Sprint end, so besides a tag not much more to do IMO.