Grouped rollout of updates

I am also interested to know if it possible to implement - Grouped rollout of updates.

Thanks

Take a look at this: https://wyday.com/wybuild/help/limit-updates.php

Hey all,

We are rolling this out now too. We are going a similarish; set the update server URL to an endpoint we control instead of S3, and then have the server selectively send the right file.

We are doing this in order to have a release, beta, and test channels, as well as deprecate our XP version while still leaving the possibility for updates to it.

If you have any questions, let me know

I am interested in doing a similar thing. I would like to release an update to a group of beta customers. I only want the beta customers to see that these is an update available. I don't want other customers to see that there is an update available until later when the group is expanded to include all customers for the final release. 

My thought is to use the same approach as outlined in https://wyday.com/wybuild/help/limit-updates.php, except use with the url that returns system.wys. Will that work? The limit-updates article describes using an updates site url including extra parameters and creating a web service to return the update file or not based on the parameters.

Can you use the same approach with the server file url and return a different server.wys depending on the parameters? e.g. http://example.com/limit-updatecheck/?update=%file%&pkey=%urlargs%

Would the first parameter still be “update=%file%” or is it different for the server file?

Thanks