lab06.md

Exercise 6 - Release Management

Learnings

1. Setting up VSTS Release Management

Setup Release Management

1. Open the most recent build in VSTS

2. In build results, follow the link to create a release.
   

1. Setup deployment to Azure Web App.
   

2. Setup Continuous Deployment by creating a trigger.
   

3. In order to automate deployment, create a Deployment Condition.
   

4. Trigger deployment automatically whenever a release has been created.
   

5. Now you can test the entire pipeline. Change someting in your code (e.g. appending a ! to the title) and check your code in. The build should be triggered automatically. The release should be created after the successful build. The release should be immediately published to Azure App Services.

Run Load Test in VSTS

1. Right-click on solution and add new Test Settings named Cloud.
   

2. Change test settings to Visual Studio Team Services.
   

3. Activate new VSTS test settings.
   

4. Change load test from Test Iterations to Run Duration as VSTS does not support test iteration setting.
   

5. Set load test location.
   

6. Set load test location.
   

7. Select the test location you want to use (ideally the location where you deployed you web app to).
   

8. Run load test.
   

9. Watch load test running in the cloud. Analyze load test results in Visual Studio and in Visual Studio Online (web report). Test test will probably fail.
   

1. Discussion points:

   • Discuss the consequences of this result (our app has a scalability problem)
   • Use Application Insights (see also exercise 4) to detect the source of the problem (requests to Blob Storage start to fail after a certain period of time).

2. In the web test's request properties, set think time to five seconds.
   

3. Re-run load test. Now it should succeed.
   

Further Ideas

If you have time left, you could additionally cover topics like:

• Setup an additional build agent in a VM