Continuous integration is a great start to a DevOps strategy. Get a demonstration for a build in VSTS using a Git repository.
- [Instructor] The next step that we usually take…in setting up a DevOps strategy is continuous integration.…Continuous integration is the development practice…that requires developers to integrate their code…into a shared repository several times a day.…The idea here is to create a lightweight build…that we can then push our code…into the system that we're using, whether it be Git or TFVC,…and compiling that code to make sure it integrates…with all the other code in the system.…We want to do this multiple times a day.…
We want those builds to run quickly…in an automated fashion as much as possible,…and we want to be able to check and see…if the code is breaking anything,…and if it's breaking, then we want to make sure…that we address that immediately.…It's a lot easier to address these defects early and often,…because now it's going to be less expensive for us to fix that.…Finding a defect later on in the process…is always more expensive than if you found it…right after it was created.…Find those defects early and often…
- What's DevOps?
- Version control Git
- Using TFVC
- Creating the continuous integration build in Git and TFVC
- Continuous delivery
- Creating and running a release management pipeline
- Continuous testing
- Implementing Application Insights
- Reading Application Insights data