Improve the open fleet build action workflow

shawaj commented 1 year ago

[ ] add frequency variants for Nebra fleets
[x] upload generated docker compose files as build artifacts and releases in this repo (for testnet and production) #701
[ ] think about moving balena deploy actions for production (not testnet) fleets out of this repo and into the device specific sub repos. this will give us more flexibility on how we trigger the actions and will allow us to space out production deployment over a 24 hour period
[ ] trigger new links to be sent to nebra hub https://github.com/NebraLtd/nebra-hub/issues/3
[ ] investigate other potential improvements

Related to #694

shawaj commented 1 year ago

Related to #670

shawaj commented 1 year ago

Just spread them out over 24 hours and add some more error notifications to slack if any fail

1st priority: commercial fleets 2nd: Nebra fleets 3rd: syncrobit and controllino and pycom 4th: other 3rd party

shawaj commented 1 year ago

NebraLtd / helium-miner-software