Process for testing updates

Ideally I would want to upload my updates (only) to a test server and my test client would check for updates there, not on the production server.

Right now there's no easy way to release to a test server, test your updates, then roll it out to a production server. We're aware this is a problem and we're adding it in the form of "update channels" that will be added in the near future.

In the meantime use separate wyBuild projects for your "test updates" and your "production updates".

Also: Is there a way to revoke updates or clear out very old updates that I know nobody will need any more?

Delete them from your servers. We don't do this automatically as part of the uploading process for a number of reasons. Plus, harddrive space is so cheap it won't make a difference for 99% of our customers to leave old files on the server. But, like I said, just delete the old updates from your server. They're no longer referenced from your *.wys file, so they're safe to delete.

Got it. Thx!

I'm replying to a very old post, I know... but there is a way to test updates and then roll them out to production. Just putting it down here in case someone else is interested.

Here's what I've done:In wyBuild, go to Download Sites, and add TWO downloadsites:1. .../App/LIVE/%file%2. .../App/TEST/%file%(Or something similar).

Now, in your app, set the wyUpdate command line parameter to use -Server = .../App/LIVE/%file%, so that your users will only use that update location.

In you test computer/app, use the -Server = .../App/TEST/%file%

Now, whenever you generate updates, just copy the wys and wyu files to the TEST folder first - your test app should get updated. When you want to push to the rest of your users, move it to the LIVE folder.

Note: It might be a good idea to prevent users other than your test user from being able to access the TEST folder.

Hope this helps someone - it's been really useful to me!