Different branches of the same app

Our app update strategy looks like this.
first, push updates to first 20 clients,
if everything goes fine, then update 50 clients more.
if everything goes fine, then update 100 clients more.
if everything goes fine, then update 250 clients more.
if everything goes fine, then update 500 clients more.
And finnaly push updates to everybody else

Previously, deploying with QtInstallerFramework, I was able to create as much branches of my app as I want ( as I able to maintain)
Like alfa1, alfa2, beta1, beta2, rc1, rc2 and so on

Looks, like applications hosted on flathub/flatpak can have only 1 special beta branch (so called flathub beta repository ) and it must be added to remotes manually…

is there another way to limit the number of clients when updating
like roll-out percent or multiple branches or whatever?

Thanks everybody in advance)))

P.S.

Of course it is possible to…
First, connect to first 20 clients via AnyDesk or TeamViewer and update from Beta repository
Then, connect to other 50 clients and update.
Then, connect to other 100 clients and update.

But we want to do it without human intervention)))

No there is no staged rollout system here.

This topic was automatically closed after 4 days. New replies are no longer allowed.