Make new releases to balenaMachine

[vipulgupta2048]

With the migration of leviathan setup to target balenaMachine, this PR enables new releases to be created on balenaMachine. Albeit the GitHub run will slow down due to the limited resources of balenaMachine.

Signed-off-by: Vipul Gupta (@vipulgupta2048) vipulgupta2048@gmail.com

[rcooke-warwick]

@vipulgupta2048 I'm interested to see if this works. WHen manually trying to balena push to our BM fleet, the builds failed (emulated as we don't have an arm builder)

[vipulgupta2048]

@rcooke-warwick yeah it didn't work: https://github.com/balena-os/leviathan-worker/actions/runs/5800359355/job/15723020380, and the reason was accurate.

My other alternative: Push a specific docker-compose that contains the balenaHub image reference to the BM fleet. Can figure out a way to auto-update version numbers in the docker-compose? The rennovate-bot can open another PR or add a commit to do exactly this: https://github.com/balena-os/leviathan/commit/ea149d835fd8b170ae9a8554e063e964c4b34af6

@klutchell would this be possible to do?

[klutchell]

A few thoughts:

• We should test builds locally to see why it fails with QEMU emulation
• We probably don't need/want to deploy to bM for open PRs, just on merge IMO
• We should use a custom Flowzone finalize action for deploy to bM

In the finalize action, you can get the current semver with a function like this.

Then we can modify the existing docker-compose file like this to replace the build arg with an image arg and then deploy-to-balena bM.

[vipulgupta2048]

On it

[vipulgupta2048]

@balena-ci I self-certify!