[Request] Build packages in github workflows

[kaysond]

Description

There are already makefile targets for various package managers. A github workflow could be set up to build all of the packages on every release.

Reason

I don't want to build the packages myself every time there's a release.

[robertbaldyga]

Hi @kaysond! Currently, Open CAS development relies on open-source community support. Unfortunately, we don’t have the resources to build, test, and support binary packages for multiple distributions and kernel versions. In the future, validated and certified binary packages may be offered as part of a premium support option. If you’re interested, we can let you know once that becomes available.

[kaysond]

Hi @kaysond! Currently, Open CAS development relies on open-source community support. Unfortunately, we don’t have the resources to build, test, and support binary packages for multiple distributions and kernel versions. In the future, validated and certified binary packages may be offered as part of a premium support option. If you’re interested, we can let you know once that becomes available.

I'm just using it for my homelab. Many open source projects release multiple binary packages automatically using github runners, enabled by github workflows (specifically the upload-artifact action) and a matrix. Here's a really good, comprehensive example:

• https://github.com/sharkdp/bat?tab=readme-ov-file#installation
• https://github.com/sharkdp/bat/blob/master/.github/workflows/CICD.yml#L156
• https://github.com/sharkdp/bat/releases/

I think it's implicit that support for automatically-built packages like this is community-only. But maybe that doesn't fit your development/business model. Nonetheless, I would strongly encourage you to implement some kind of automatic packaging because it reduces friction for adoption.