#SPSDetroit 2017 improving #DevOps using #microsoft business productivity tools and more
1 like254 views
The document discusses the enhancement of DevOps practices using Microsoft's business productivity tools focusing on reducing deployment times while maintaining quality. It emphasizes the importance of automation, efficient version control through Git, and collaboration among cross-functional teams. Key points include improving deployment frequency, reducing failure rates, and the necessity of peer reviews and automated testing to foster team growth and productivity.
#SPSDetroit 2017 improving #DevOps using #microsoft business productivity tools and more
- 1. Improving DevOps using Microsoft's Business Productivity Tools and more Real-life experience that leverages Microsoft tools and DevOps processes Haniel Croitoru & Vincent Biret December 2, 2017 #SPSDetroit
- 3. Don’t forget to complete your session evaluations WSU-PUBLIC
- 4. VINCENT BIRET We’re passionate about DevOps and we work at . DEVELOPER | OFFICE 365 MVP HANIEL CROITORU LEAD CONSULTANT | OFFICE 365 MVP
- 5. Reduce time between committing a change to a system and committing it to production while maintaining high quality DEVOPS GOALS • Improved deployment frequency • Faster time to market • Lower failure rate of new releases • Shortened lead time between fixes • Faster mean time to recovery Development Quality Assurance Operations
- 6. Intended to be a cross-functional mode of working DEVOPS TOOLCHAIN
- 7. DEVOPS
- 9. DevOps teams focus on development, testing, and releasing solutions DEVOPS TEAM Developers QA Operations
- 10. External Teams Management Business Analysts End Users Clients However, extended team is not included in the process DEVOPS TEAM Developers QA Operations
- 11. DEVOPS BASICS
- 12. DevOps, from the delivery team perpective is about automating, releasing frequently and leveraging telemetry as well as feedback to improve solutions DEVOPS BASICS
- 13. A few technologies and practices that’ll allow your team to scale LIFE SAVERS
- 14. Git is great with branches and cross platform, it has become an industry standard Gitflow is a great process for DevOps teams and allows them to scale seemlessly GOOD SCM PRACTICES IS KEY Git is a decentralized source control technology Branches are cheap Merging is not a nightmare Cross platform Lot of tools Git flow is a process model for branch management Focused work Easy context switching Standard and no thinking required
- 15. Pull requests are a great way to help your team grow and to improve the quality of the code PEER REVIEWS AND QUALITY « Here are a bunch of changes in the code, please review it and make it part of the main code » Also check if changes: Build Pass unit tests Pass static analysis gate (code quality) Have associated work items (context/documentation) And allows: For discussion The team to grow together
- 16. Automation of almost everything is a key to your DevOps team success and productivity AUTOMATE AND FAIL FASTER Automated Unit tests ran every build Allow team to fail faster and to catch runtime issues earlier Automated Builds on every push/PR Allow team to leverage a great toolset and avoids broken code Automated Releases on new builds Allow team to ship faster, with less errors, effortless and more often Automated Notifications Allow team to focus on creating value, not updating people
- 17. Versioning not only the binaries but also configuration and service template will allow you to deploy any version with great fidelity and enable test in production as well as advanced debugging scenarios VERSION EVERYTHING Configuration should be automated/versioned Avoid a great source of errors Allows rapid deployment of specific versions with corresponding configuration Code should be Packaged, even if not a library Allows rapid solution deployment Allows solution « composition » Service provisioning should rely on templates
- 18. DEMO
- 19. Goal is to unite all stakeholders COMMUNICATION GOALS External Teams Management Business Analysts End Users Clients Developers QA Operations
- 20. DEMO
- 21. We work hard, we party hard! SharePint! 4:00pm–6:00pm Common Pub Detroit 5440 Cass Ave PLEASEDRINKRESPONSIBLY. WEWILLBEHAPPYTOCALLACABFORYOU
- 22. Don’t forget to complete your session evaluations
- 23. Thank You! Organizers, Sponsors and YOU for making this possible. Vincent Message Me On LinkedIn or Email linkedin.com/in/vincentbiret vincent@2tolead.com Haniel Message Me On LinkedIn or Email linkedin.com/in/hanielcroitoru haniel@2tolead.com
Editor's Notes
- #7: Code — code development and review, source code management tools, code merging Build — continuous integration tools, build status Test — continuous testing tools that provide feedback on business risks Package — artifact repository, application pre-deployment staging Release — change management, release approvals, release automation Configure — infrastructure configuration and management, Infrastructure as Code tools Monitor — applications performance monitoring, end–user experience
- #25: Background image source http://www.silicon.co.uk/wp-content/uploads/2015/05/M2M.jpg
- #30: Runners: take care of running the tests and provide the infrastructure for (memory, processes…) Asseration libraries: « ways » to write your unit tests Emulators (or environments): context within the tests will run (server with node, browser, emulated browser…) Reporters: take care of writing down tests results in comprenhensive format Frameworks: provide a suite of functionnalities to help implement testing Stubing/Mocking-Faking/Spying: allows you to isolate the tested code and/or observe behavior