[Feature request]: build workflow: upload packages to github cache #19
Description
Use Case
As a contributor that has no idea if my changes work, it would be great if PRs could produce rpm/deb packages that I can download.
https://github.com/OpenVoxProject/shared-actions/blob/main/.github/workflows/build_ezbake.yml and https://github.com/OpenVoxProject/shared-actions/blob/main/.github/workflows/build_vanagon.yml produce packages and upload them to S3. This is currently intended to make build and upload official releases.
Describe the solution you would like
I think it would be great if we could use actions/upload-artifact to upload the rpm/deb files, for each CI run, to GitHub.
That would make it easier for us to test builds and rerun CI jobs , without overwriting the official artifacts s3 bucket.
Rerunning would be great, especially for openvoxdb and openvoxserver, because they currently pull in ezbake main branch. So to test ezbake changes, we can rerun pipelines in openvoxdb/openvoxserver (I know this sucks and ezbake should be pinned, but it isn't right now). To make this easier, it would be great if the tag input for the build workflows would be optional. if it's set to tag, assume it's an official build and upload it to s3, if it's main, build the main branch of openvox/openvoxserver/openvoxdb and only publish the packages to github, not s3.
Describe alternatives you've considered
No response
Additional context
No response