Build it, Test it, Ship it: Continuous Delivery at Turner Broadcasting System, Inc.
•Transferir como PPTX, PDF•
2 gostaram•1,245 visualizações
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Build it, Test it, Ship it: Continuous Delivery at Turner Broadcasting System, Inc.
Semelhante a Build it, Test it, Ship it: Continuous Delivery at Turner Broadcasting System, Inc. (20)
Mais de Atlassian
Mais de Atlassian (20)
Último
Último (20)
Build it, Test it, Ship it: Continuous Delivery at Turner Broadcasting System, Inc.
- 2. Continuous Delivery at Turner Broadcasting System, INC Daniel Wester Chief Engineer, Turner Broadcasting System, INC 2 Built it, Test it, Ship it
- 3. Who we are 3 and more…
- 5. Continuous Integration 5 Code committed to SCM Central process retrieves code from SCM Code compiled and packaged Automated tests Artifact produced
- 7. 7 “What makes continuous deployment special is deploying every change that passes the automated tests (and optionally a short QA gate) to production. Continuous deployment is the practice of releasing every good build to users – a more accurate name might have been “continuous release”.” From: Continuous Delivery vs Continuous Deployment by Jez Humble http://continuousdelivery.com/2010/08/continuous-delivery-vs-continuous-deployment/ Copyright © 2011 Jez Humble - All Rights Reserved. This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License (http://creativecommons.org/licenses/by-sa/3.0/us/ ) Continuous Deployment
- 8. 8 “Implementing continuous delivery means making sure your software is always production ready throughout its entire lifecycle – that any build could potentially be released to users at the touch of a button using a fully automated process in a matter of seconds or minutes.” From: Continuous Delivery vs Continuous Deployment by Jez Humble http://continuousdelivery.com/2010/08/continuous-delivery-vs-continuous-deployment/ Copyright © 2011 Jez Humble - All Rights Reserved. This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License (http://creativecommons.org/licenses/by-sa/3.0/us/ ) Continuous Delivery
- 13. Our journey starts 13 •CNN.com created in 1995 •Everything manual •Dev environments shared •A lot of development being done in production •No configuration management
- 14. Conversation 14 Customer Developer Hey! This feature no longer works! It worked 10 minutes ago. Oops! That was me. Fixing it now.
- 16. Shell script deployments 16 • Set of shell scripts monitoring a directory handles deployments. • UI created in front of folder to allow developers select files to promote to an environment.
- 17. Conversations 17 Dev Lead Developer Dev Lead Developer The Customer reported that this just broke – who changed something? It wasn’t me – the change I just pushed out was for this other thing Did you push out the new configs as well? Oh…
- 19. Partial CI Builds 19 •Replaced shell scripts with Ant and CI server •UI allow Developers select files •Files tagged in SCM with environment and date •Backend managed deployment to environments
- 20. Demo 20
- 23. Challenges with partial builds 23 •Environments are not re-creatable •Not scalable as development team grows •Does not scale for large changes
- 24. CI with manual deployment 24 •Web Applications •Compiled applications •Manual deployments done through Configuration Management tools
- 26. Challenges with CI/manual 26 •Files are passed around •Manually maintained •Builds are incremental, but release is not •Prone to environmental inconsistencies •Intra-project differences
- 27. CNN.com Elections 27 •AJAX based application •Iteration developed •One build plan per environment •Deployment to production - manual
- 29. Conversations 29 Dev Lead Developer Dev Lead QA I thought that you said that the fancy feature would be in the build? Done Oh! I forgot to merge it in time. Can you do another build? The new build that was just delivered broke a lot of functionality.
- 31. Integration with CM frameworks 31 •Integrated with CM for external projects •Infrastructure driven Poll external repository Create internal build Package for remediation Send onto internal remediation
- 32. Not just for SCM based SW 32
- 35. Continuous Delivery 35 • “A new” web development platform brought in •Requirement of “zero-touch” of production •Single build for all environments. Developer commits Build • Unit tests • Functional tests Packaging • Compressed package created • Sent to central artifact repository Auto- Remediation • CM Framework receives request from CI Server Developer and QA performs final verification tests Testing completed and Customer “blesses” a build Development selects build to promote CM Framework receives request from CI Server
- 37. Continuous Delivery Iteration 2 37 •Monitoring system integration •Build promotion history •Remediation can occur on Plan or job
- 38. Demo 38
- 39. Why integrate build sys and Release Mgmt? 39 •Source Code Correlation •Guaranteed no manual steps •For the developers – one tool
- 40. Conversations 40 Dev Lead Developers Dev Lead QA/Custome r I see you have changes lined up– are they ready to go into the staging env? Build 232 is in staging Yes. Build 232 looks good. Dev Lead Build 232 going out to prod
- 41. What the NOC sees 41
- 42. What the QA team sees 42
- 43. What the Developer sees 43
- 44. What the Infrastructure team sees 44 •Concentrate on automation •Developer accountability for production increases •Less firefighting •Next project…
- 45. What Management sees 45 •NOC Awareness •Unit and Functional tests •QA Tested •Automatic deployments with rollback capability •Speed to market with minimal delays •Efficiency in the process •Removal of artificial roadblocks
- 47. Challenges 47 •Full build concerns from various parties •Development and Infrastructure teams must be in sync •Use SCM, Build and CM systems for their purposes •Initial investment cost for new project types •One artifact to rule all environments
- 48. Impact 48 •Delivery time to market - down •Quality of deliverables - up •Cultural change (more collaboration) •Change tracking on source changes
- 49. 49 Continuous delivery requires sharing operational ownership between dev & ops, and lets us rapidly develop sites in parallel #summit11