Hi! Thanks for your reply @Ryan Hill . Currently we have 3 deployment slots on our web-app. Dev, QA and Production. In our normal workflow, after a developer has made changes he is satisfied with, he would create a pullrequest towards master in our Dev-environment. This will then automatically trigger a build and release pipeline that deploys this new version of our webapp to our Dev-environment. After testing, we would then merge the PR to master, and push the code changes to QA and Prod as well.
But, the problem arises when multiple developers have big pull requests - and would want to test their features in the cloud at the same time. Only ONE branch/pr could be deployed to the Dev-slot at a single time - meaning that developers need to "reserve" the Dev-environment for testing. What we would ideally like, is that when a pull request is created towards master, the code would be built and deployed to a unique Pull-Request environment. Meaning that we dynamically have X development environemts, one for each active pull request. This would allow the master-Dev-environment to be stable, and all the changes made by different developers would live in their own PR-deployed environment.
I guess it is similar to what is suggested here, but that guide is based on AKS. I wonder if it is possible to do this with azure web apps?
https://devblogs.microsoft.com/devops/review-apps-in-azure-pipelines/