Practical Continuous Deployment, Devoxx UK 2015
3 likes1,219 views
Steve Smith advocates for continuous deployment and discusses how to implement it practically. He outlines the stakeholders in continuous deployment, including users, managers, developers and admins. He then describes a branching workflow for development that incorporates continuous integration, testing on pull requests, releasing to staging, and promoting to production. Automation and removing bottlenecks are important principles. Clear motivation, cooperative tools and people, and a branching workflow are key to successful continuous deployment.
More Related Content
Similar to Practical Continuous Deployment, Devoxx UK 2015 (20)
Practical Continuous Deployment, Devoxx UK 2015
- 1. @tarkasteve #practicalcd Practical Continuous Deployment Steve Smith @tarkasteve #practicalcd https://developer.atlassian.com/blog https://haltcondition.net go.atlassian.com/devoxxuk15
- 3. @tarkasteve STEVE SMITH • DEVOPS ADVOCATE • ATLASSIAN • @TARKASTEVE
- 4. @tarkasteve What I’ve been up to
- 10. @tarkasteve Why Leo Reynolds / Flickr
- 19. @tarkasteve How?
- 20. @tarkasteve BRANCH Development workflow CONTINUALLY TEST PULL REQUEST DEPLOY (STAGING) PROMOTE BRANCH TRACK REQUESTS
- 22. @tarkasteve stable master branch master Work on a branch isolated feature work feature/JIRA-123
- 23. @tarkasteve Continuously test stable master branch master isolated feature work feature/JIRA-123
- 24. @tarkasteve Pull Request feature/JIRA-123 master technical debt O(n!) algorithm bad API decision human judgement needed ?
- 42. @tarkasteve Key Points CLEAR MOTIVATION COOPERATIVE TOOLS AND PEOPLE BRANCHING WORKFLOW