Allow multiple staging deployments
I would like to have more than 1 staging deployment in a cloud service. Ideally the number of staging deployments would not be fixed, and could be named.
Some scenarios I'd like to use this for:
1. Deploy multiple versions of an application to the various staging deployments (e.g. staging 1 and staging 2) and test them in the Azure infrastructure, and then swap the chosen one into production when it is deemed ready.
2. Keep an old battle tested production deployment in reserve in a staging deployment when wanting to deploy multiple new versions of a project. An example sequence of events:
a - Production deployment (alpha) is running. Staging deployment (beta) has new code ready for production.
b - Production and staging are swapped. Production is now in staging.
c - The production deployment (beta) is new but not battle tested as staging (alpha), however another new version (gamma) is needed. I would like to keep the battle tested version (alpha) that's current in staging around, but if I have to deploy another new version (gamma) over staging (alpha), I lose my battle tested version (alpha).
Great feedback, thanks! We don’t have any plans to support this yet, but we’ll look into in the future.
For anyone who is interested, I recently upvoted this. But after studying the new deployment slots in the new Azure App Services, I think they do allow this functionality. I have recently created multiple deployment slots: staging, alpha, and beta (in addition to the prod slot obviously ). I am able to publish to any individual slots with customizable app settings/conn strings ("sticky" slot settings ). I also can swap any slot with any other slot. So if you arent married to cloud services exclusively (I think there is a migration path otw?), you might check out the App Services.
Alan M commented
Uservoice admins, please combine the votes from this post to the one Michael links to in the comments.
Michael Paterson commented