How to handle private beta?

I'd to know how to handle the upgrade to a beta version update only for that customers subscribed to the private beta test program, but the others customers don't have to know about the new beta release when wyUpdate check for update.

Thanks.Cristiano

Yes,I'm looking for something very similar. Based off of our client's login information, I would like to control who gets an update or not. I don't think this is handled out of the box so I'm hoping someone can point me in the right direction in the code. I'm thinking a call to a service to determine if update is needed.

Thanks!

Another scenario is when I have to send a patch only for a particular customer, and after tried it, send the official patch for all.

I think this may be the way to do it.http://wyday.com/wybuild/help/limit-updates.php

To limit updates, as buzz already pointed out, see our Limit updates article.

Another scenario is when I have to send a patch only for a particular customer, and after tried it, send the official patch for all.

We're making this easier in wyBuild 2.7. Right now the only way to do this is to override the "server site" (the site where the *.wys file is hosted) to where you're storing the temp or beta version of your software. After the updates have successfully been tested you can roll them out to all your users.

Does that make sense?

Using the override of the server address is a solution, but this means that I have to implement a web service to invoke before to check to get the temp-address.For now, I can wait hoping that the 2.7 version exit before (in Agile style ).

I think that the simple possibility to add metadata (list key/value of string) to the update like the changelog, could permit to validate the update before calling download/install.

Thanks.

Hi, this is of great interest to me as well...

Can I float an idea, and I'd welcome some feedback on whether it's workable, especially from a customer experience perspective.

I want to be able to test with a specific set of users, whom I can partition off at the IP level - for them the updates server is reachable, but for others it's not. Would it make sense to add this server to the server list (for updates and files)?

My thinking is:1. for all other users, they get the update from the standard server, and a call to the 'beta' server fails2. for the beta users, the client checks first the normal server, than the beta server and get the latest update from the beta server.

Then all I need to do is make sure I only upload the beta updates to the beta server.

Thank you,Marcin.

Would this work - and are there any adverse consequences I should be aware of (errors, long delays/wait times, etc)?

Or maybe I'm over-complicating it - do i just set AutoUpdater.wyUpdateCommandline in my beta-relese code to -server="<url>"

ie in c# autoupdater1.wyUpdateCommandline = @"-server=""http://betaserver/update/wyserver.wys""";

Hey Marcin,

Yes the -server="..." commandline argument is the best for 2.6.x. But we're working the make it even easier for 2.7.

Is there an idea when 2.7 will be ready? Eager for this feature. Thanks.

2.6.15 is coming out today. 2.7.0 is coming in about a month.

Reply
Discard post