54 votesJens Spaniel shared this idea ·
Thanks for the feedback! We are working on enabling this feature.
An error occurred while saving the commentJens Spaniel commented
I miss this feature, too. Even I read https://sunithamk.wordpress.com/2015/10/23/faq-deployment-slots-with-azure-web-apps/ we have a different setup. Our continuous integration deploys to Slot "Integration", where we always have the latest version. Out testers do not always to their tests on the latest version because this can change every hour. So the testers use their own slot "Staging". If the start the test for a build they get the latest version from the Integration-slot. As long as they do their tests, which can take hours to days, there will be new builds deployed to "Integration". But this does not effect the tests on the deployment slot. If a build of the deployment slot was not tested successfully, the testers get the next version from "Integration". But it the test was successful, the build is moved to the slot "release candidate". After our customer agrees on getting the new build we move first the lasted productive build to the slot "Last" and then the build from "release candidate" to productive.
For this workflow a copy would be better than a swap.
So again our slots:
Integration – Staging – Release Candidate – Productive – LastJens Spaniel supported this idea ·