![]() ![]() Therefore, if you were to run load tests against the QA slot, it would impact the performance of the Production slot as well. Each slot of the web application shares the same resources. In the Dev and QA environments, you will also want to run tests such as load and performance tests.įirst, we will address testing. ![]() You also must deploy the database and other dependencies. However, rarely are you only dealing with the web application. The thinking was they would copy the files to Dev, then swap to QA, and finally swap into Production. One example I witnessed had two deployment slots: Dev and QA. Often when I see people using deployment slots in their pipelines, they attempt to swap across environments. The goal of this post is to focus on best practices and anti-patterns. The deployment slot has its own hostname and is a live app.ĭeployment slots are extremely powerful, but care must be taken when you start to integrate them into your DevOps Pipeline. In the Azure Portal, in the Azure App Service resource blade for your Web App, you can add a deployment slot by navigating to “Deployment slots,” adding a slot, and giving the slot a name. Using deployment slots can allow you to do this with zero downtime. The goal of DevOps is to continuously deliver value. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |