VSTS Continuous Integration and Deployment

Transcript

2. VSTS CI & CD @miguelcruznet mcruz@plainconcepts.com
3. INDEX 1. TFS XAML builds 2. VSTS task based builds/releases 3. Continuous Integration 4. Continuous Delivery 5. CI + CD flow overview 6. Branching strategies 7. Custom tasks 8. Running builds during pull request 9. Task groups 10.Variables 11.Credential Management 12.Examples 1. .Net Framework 2. NetCore 3. Javascript 4. Publishing to Azure 13.Practice
4. TFS XAML BUILDS Key Features: • Configured through Visual Studio UI • Developer Unfriendly
5. VSTS TASK BASED BUILDS/RELEASES Key Features: • Configured through web • Developer friendly • Marketplace • Custom Tasks
6. CONTINUOUS INTEGRATION * Credits: Thoughtworks
7. CONTINUOUS DELIVERY * Credits: Thoughtworks
8. CI + CD FLOW OVERVIEW
9. BRANCHING STRATEGIES
10. CUSTOM TASKS Supported languages: Powershell & Javascript
11. RUNNING BUILDS DURING PULL REQUEST
12. RUNNING BUILDS DURING PULL REQUEST
13. RUNNING BUILDS DURING PULL REQUEST
14. RUNNING BUILDS DURING PULL REQUEST
15. TASK GROUPS
16. TASK GROUPS
17. TASK GROUPS
18. VARIABLES Variable scopes: • Library • Release • Environment
19. CREDENTIAL MANAGEMENT Purpose: • Inject credentials into config files during release • Store credentials and per-environment information in variables
20. EXAMPLE: .NET FRAMEWORK BUILD
21. EXAMPLE: NETCORE BUILD Build
22. EXAMPLE: JAVASCRIPT BUILD
23. EXAMPLE: PUBLISHING TO AZURE Release
24. PRACTICE Requirements: 1. Branch policies with mandatory build check during PR 2. CI: build runs after PR is completed 3. CD: build completion triggers release, which deploys into Azure 4. Credentials management: settings are replaced during deploy 5. No down-time deploying through slot
25. THANKS! @miguelcruznet mcruz@plainconcepts.com