DevOps ci/cd with Microsoft vsts and azure
Download as PPTX, PDF7 likes2,494 views
The document outlines a workshop on DevOps, focusing on Continuous Integration (CI) and Continuous Delivery (CD) practices, led by Murughan Palaniachari. It highlights best practices for CI/CD, such as maintaining a single source repository, automating builds, and ensuring software quality through automated testing. Additionally, it emphasizes the importance of feedback and telemetry in enhancing software development processes and includes various resources for further study.
DevOps ci/cd with Microsoft vsts and azure
- 1. DevOps CI/CD with by Murughan Palaniachari
- 2. http://www.unicomlearning.com/2017/Devops_Microservices_and_Containers_Summit_Bangalore/ Who am I? Murughan Palaniachari DevOps Coach @ Euromonitor Certified DevOps guy, Speaker, Blogger and Trainer Organizer - Cloud and DevOps meetup https://elevate-org.com/ https://devopsgames.com/ https://in.linkedin.com/in/murughan @Murughan_P
- 4. Workshop Goal • DevOps • Continuous Integration • Continuous Delivery/Deployment • Azure cloud • Monitoring https://twitter.com/Murughan_P
- 10. Continuous Integration best practices • Maintain a Single Source Repository. • Automate the Build • Make Your Build Self-Testing • Everyone Commits To the Mainline Every Day • Every Commit Should Build the Mainline on an Integration Machine • Fix Broken Builds Immediately • Keep the Build Fast • Test in a Clone of the Production Environment • Make it Easy for Anyone to Get the Latest Executable • Everyone can see what's happening • Automate Deployment https://martinfowler.com/articles/continuousIntegration.html https://twitter.com/Murughan_P
- 11. Continuous Integration best practices • Everything in Source Control • Every check-in goes through pull request • Make your build self-testing • Adopt trunk-based development practices • Continuously build, test, and integrate our code and environments • Build a fast and reliable automated validation test suite • Ensure tests run quickly (in parallel, if necessary) • Write our automated tests before we write the code (“test-driven development”) https://twitter.com/Murughan_P
- 15. Workshop - Continuous Integration with VSTS https://www.visualstudio.com/team-services/ DEMO/WORKSHOP https://twitter.com/Murughan_P
- 16. Trunk based development & pull request https://twitter.com/Murughan_P
- 19. Principles of Automated acceptance testing • Treat acceptance tests like production code • Collective ownership of acceptance tests • Quality is everybody’s responsibility • High quality test suites are continuously curated by testers and developers working together • Ensure tests are independent • Acceptance tests own their data • Always interact with the system under test the same way a user would • Use record-playback tools to build your suite https://continuousdelivery.com/ https://twitter.com/Murughan_P
- 20. Code Analysis - Sonarqube https://twitter.com/Murughan_P
- 21. Continuous Delivery The ability to get changes of all types— including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way. Jez Humble https://twitter.com/Murughan_P
- 22. Why Continuous Delivery • Increase software quality and stability • Make releases painless, low risk events • Reduce time to market • Increase customer and employee satisfaction • Reduce cost of ongoing software development https://continuousdelivery.com/
- 23. Key Principles • Computers do repetitive tasks, people solve problems • Build quality in • Work in small batches • Everyone is responsible • Relentlessly pursue continuous improvement https://continuousdelivery.com/
- 24. Continuous Delivery best practices • Enable on demand creation of dev, test, and production environments • Make infrastructure easier to rebuild than to repair • Modify our definition of development “done” to include running in production-like environments • Build a fast and reliable automated validation test suite • Catch errors as early in our automated testing as possible • Automate as many of our manual tests as possible • Integrate performance testing into our test suite • Integrate non-functional requirements testing into our test suite http://itrevolution.com/devops-handbook https://twitter.com/Murughan_P
- 25. Continuous Delivery best practices • Pull our andon cord when the deployment pipeline breaks • Enable automated self-service deployments • Integrate code deployment into the deployment pipeline • Decouple deployments from releases • An architecture that enables productivity, testability, and safety • Architectural archetypes: monoliths vs. Microservices • Use the strangler application pattern to safely evolve our enterprise architecture • Automate and enable low-risk releases • Architect for low-risk releases http://itrevolution.com/devops-handbook https://twitter.com/Murughan_P
- 26. Workshop Continuous Delivery Azure Subscription https://twitter.com/Murughan_P DEMO/WORKSHOP http://azure.microsoft.com/free
- 28. Amplify feedback best practices •Create application logging telemetry that helps production •Use telemetry to guide problem solving •Enable creation of production metrics as part of daily work •Create self-service access to telemetry and information radiators •Find and fill any telemetry gaps •Application and business metrics •Infrastructure metrics •Instrument and alert on undesired outcomes •Use telemetry to make deployments safer http://itrevolution.com/devops-handbook https://twitter.com/Murughan_P
- 29. Amplify feedback •Have developers initially self-manage their production service •Integrating a/b testing into our feature testing •Enable coordination and scheduling of changes •Enable peer review of changes •Enable pair programming to improve all our changes •Evaluating the effectiveness of pull request processes •Fearlessly cut bureaucratic processes http://itrevolution.com/devops-handbook https://twitter.com/Murughan_P
Editor's Notes
- #14: Microsoft also invests heavily in the open source ecosystem and enables you to keep your existing investments in open source tools while potentially enabling integration with our own technologies. In this slide you can see a number of different open source products we have interoperability with which play different roles across the entire application lifecycle. These open source tools often play a part in more than one aspect of the product lifecycle, but they are listed here based on the primary integration point with a Microsoft technology. Last but not least, I’d like to point out that the Microsoft Cloud OS platform where you might decide to host your application supports various programming languages like node.js, php, and java as well as underlying open source operating systems like Linux.
- #15: Features in Visual Studio Online get released once every three weeks and around once per quarter those features get rolled up and put into an update which goes into the on-premises Team Foundation Server. So no matter whether you prefer to do your business in the cloud, hybrid, or on-premises, Microsoft has you covered.