Azure Pipeline in salsa yaml
Download as PPTX, PDF0 likes209 views
This document discusses Azure Pipelines and common misconceptions about it. It notes that Azure Pipelines can be used for both cloud and on-premises workloads, not just Microsoft technologies, and that maintaining agents is simplified. The document traces the history of Azure Pipelines and its predecessors. It promotes the benefits of defining pipelines in YAML, including storing them in source control, easy copying between repos, and support in Visual Studio Code. Future improvements may include multi-stage pipelines and releasing directly to environments using YAML.
Azure Pipeline in salsa yaml
- 1. #azuresatpn Azure Saturday 2019 Azure Pipelines in salsa YAML
- 2. #azuresatpn
- 3. #azuresatpn Misconception #1 – Everything runs on azure
- 4. #azuresatpn Misconception #1 – Everything runs on azure Core Pipeline services On Premises Aws / google / other cloud Agent Server
- 5. #azuresatpn Misconception #2 – only for the cloud • Azure DevOps server runs on azure • Everything else can be on-premise • Agents • Source control • Deploy target • Third party system • Etc.
- 6. #azuresatpn Misconception #3 – It is only for Microsoft stuff • Runs on Mac and Linux • Java, Python, C++, .NET, Angular, and more • Deploy on azure / other cloud / on-premise • Integrate with other: • Source control • CI / CD technologies • Extensible with addin and a full marketplace
- 7. #azuresatpn Misconception #4 – Complex to maintain • Hosted agents managed by MS • On-Premise agent experience: • Unzip and config • Auto Update • Automatic Maintenance • Centralized control • Centralized security
- 8. #azuresatpn Litte bit of history • 2005: TFS CI === MsBuild • 2010: TFS CI === Workflow Foundation (complex and difficult to use) • 2015: TFS / Azure DevOps CI === Web Editor, Task based • 2018: TFS / Azure DevOps CI === YAML file in source control. Back to the basic
- 10. #azuresatpn Why YAML: Everything in source control Base CI Code Quality CI Release Package
- 11. #azuresatpn Why YAML: Easy to copy definitions between repos Base CI Code Quality CI Release Package
- 12. #azuresatpn Why YAML: Follow branches
- 13. #azuresatpn Why YAML: Base Template definition Nuget Base CI Angular Repository of Base YAML Templates Project Repo Base CI References
- 14. #azuresatpn Why YAML: Visual Studio Code Addin Intellisense Validation Task List
- 15. #azuresatpn Why YAML: Easy convert from existing Pipelines
- 16. #azuresatpn Demo: Migration to YAML
- 17. #azuresatpn Future • Multi-stage pipeline • Release on environment with YAML • https://dev.azure.com/mseng/AzureDevOpsRoadmap/_workitems/re centlyupdated
- 21. #azuresatpn