Migrating to Continuous Delivery with TFS 2017 - Liviu Mandras-Iura
•
0 j'aime•850 vues
The presentation will talk about Continuous Delivery best practices and how one can migrate from not doing CI/CD at all to a proper CD process while acknowledging that there are so much many intermediary states that still bring value. The presentation will have the main focus on the journey from one state to the other infused with the speaker’s own experience on the process. There will be a showcase of a demo project that will exemplify how to implement a simple automated deployment pipeline using TFS 2017. This will show the general capabilities of TFS 2017 which is now quite a capable tool as opposed to previous versions. The presentation will target Architects, Team Leads, DevOps engineers or anyone that has to implement Continuous Integration/Delivery practices in a team.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (10)
Similaire à Migrating to Continuous Delivery with TFS 2017 - Liviu Mandras-Iura
Similaire à Migrating to Continuous Delivery with TFS 2017 - Liviu Mandras-Iura (20)
Plus de ITCamp
Plus de ITCamp (20)
Dernier
Dernier (20)
Migrating to Continuous Delivery with TFS 2017 - Liviu Mandras-Iura
- 1. Sailing towards Continuous Delivery Liviu Mandras-Iura @ITCAMPRO #ITCAMP17Community Conference for IT Professionals
- 7. Lower Risk, higher ROI
- 10. The challenge!
- 11. There is no free lunch… Initial cost in tooling/hardware Cultural shift Knowledge cost
- 12. Hard doing it by the book
- 13. Great news: you don’t have to
- 14. The bottom line CD will give you: + Lower risk + Frequent value delivery + Higher quality - Short term costs
- 15. GOLD SILVER PARTNERS PLATINUM POWERED BY @ITCAMPRO #ITCAMP17Community Conference for IT Professionals Many thanks to our sponsors & partners!
- 16. Liviu Mandras-Iura 30 years old Software Architect @ Into programing for 1/3 @ITCAMPRO #ITCAMP17Community Conference for IT Professionals
- 17. Asses initial position The deployment pipeline basics Pipeline stages Agenda
- 18. Everything Manual Continuous Delivery Continuous Deployment Continuous Integration You might be here
- 21. Continuous delivery can scale down
- 23. Artifact repository Source code ProductionPerformance Stage User Acceptance Stage Commit Stage Acceptance Stage BIN BIN Deployment pipeline
- 24. Where do you start?
- 25. Start automating your current build process
- 26. My Process Typical SCRUM-BAN process Releases every 2 weeks Gitflow branching model
- 28. My Environment Machine1 Machine 2 DEV ACCTEST QA TRN PRODUCTION Windows Server 2008 R2 IIS 7.5 .NET 4.5.2 Windows Server 2012 R2 IIS 8.5 .NET 4.5.2
- 29. The Commit Stage ProductionPerformance UATCommit Acceptance
- 30. Commit Stage Rule: Commit often on trunk No branching
- 31. Commit Stage But Gitflow = branches (What the hack?!)
- 32. Commit Stage Rule: Fast build process
- 33. Commit Stage
- 34. Commit Stage Rule: Run test suite before committing
- 35. Commit Stage People forget to run the test suite…
- 36. Commit Stage Solution: preflight build
- 37. Commit Stage Create a good test suite Don’t use broken builds Keep the build green Fast fix or revert Shared code ownership Do TDD
- 38. Commit Stage
- 39. Commit Stage
- 41. Commit Stage Dev CI Preflight Code analysis DEV Release Artifact Repository BIN Commit Stage
- 42. The Acceptance Stage ProductionPerformance UATCommit Acceptance
- 43. Acceptance Stage More important than you think …yes, you, the developer
- 44. Acceptance Stage Derived from acceptance criteria
- 45. Acceptance Stage Executable specifications Given some context When some action is performed Then observable effects happen
- 46. Acceptance Stage Good acceptance tests = Carefully designed tests
- 47. Acceptance Stage Tests are first class citizens Production code Test code
- 48. Acceptance Stage Test state management
- 51. Acceptance Stage What we did…
- 52. Acceptance Stage Devs & QA shared ownership
- 53. Acceptance Stage Acceptance Specification “Given-When-Then” Test Implementation DSL No UI references Test Framework Window Driver Pattern Page Object Pattern Web Driver Selenium
- 54. My Pipeline The pipeline so far…
- 55. My Pipeline Source code Commit Stage Acceptance Stage DEV Artifact Repository BIN
- 56. The Performance Stage ProductionPerformance UATCommit Acceptance
- 57. Performance Stage Derived from acceptance tests
- 58. Performance Stage Get correct metrics!
- 59. Performance Stage No automated performance testing
- 60. The User Acceptance Stage ProductionPerformance UATCommit Acceptance
- 61. User Acceptance Stage DEV Commit Stage Dev CI Preflight Code analysis Release Artifact Repository BIN QA BIN UAT Stage
- 62. Production Stage ProductionPerformance UATCommit Acceptance
- 63. Production Stage One click deploy and rollback
- 64. Production Stage Zero down time deployments
- 65. Production Stage Users Router X X+1 Canary release
- 66. Production Stage Users Load Balancer Web Server DB Server X X+1 X X+1 Blue-Green deployment
- 67. Production Stage We take advantage of timezone difference
- 68. My Pipeline MergeSource code UAT Stage LiveCommit Stage Acceptance Stage
- 69. My Pipeline But there is more…
- 70. Acceptance Stage My Pipeline Merge Source code Commit Stage Dev CI Release Deploy & Run tSQLt Tests Deploy DEV DEV Run Acc Tests ACC TEST Deploy Live PROD UAT Stage QA BIN BIN BIN BIN BIN
- 71. Acceptance Stage My Pipeline Merge Source code Commit Stage Dev CI Deploy & Run tSQLt Tests Deploy DEV DEV Run Acc Tests ACC TEST Deploy Live PROD UAT Stage QA BIN BIN BIN BIN BIN
- 73. Summary Reliable build process Push button release and rollback Separate DEV cycle from UAT cycle Some level of quality built in Time
- 74. Summary When to stop? It depends!
- 76. Summary Business testing lags behind
- 77. Tools and processes can help you… If you use them
- 78. Skills are required but don’t overthink it Just start and evolve!
- 83. ThankYou! @ITCAMPRO #ITCAMP17Community Conference for IT Professionals
- 84. @ITCAMPRO #ITCAMP17Community Conference for IT Professionals Q & A