Continuous Delivery Workshop

Transcription

1 Continuous Delivery Workshop deployment pipelines Workshop materials created by Jez Humble, Martin Fowler, Tom Sulston, & Neal Ford

2 deployment pipelines tests, synergistic practices, incremental deployment data & infrastructure

3 Who are You? Manager DBA BA Operations Developer UX QA

4 Agile Transformation Manager DBA BA Operations Developer UX QA

5 Continuous Delivery Manager DBA BA Operations Developer UX QA

6 It s a people problem.

7 The Dangers of Silos The Tragedy of the Commons

8 Release Cadence

9 Release Cadence Mary Poppendieck Tom Poppendieck How long would it take your organization to deploy a change that involves just one single line of code? devopsy.com/blog/2013/08/16/devops-kata-single-line-of-code/ Can you do this on a repeatable, reliable basis?

10 Continuous Delivery Metrics lead time the time between the initiation and completion of a production process. cycle time the total elapsed time to move a unit of work from the beginning to the end of a physical process

11 Continuous Integration Integration early and often. Everyone checks into trunk at least once a day.

12 1200 Bring the pain forward. 900 eager vs. late pain time

13 Continuous Integration Integration early and often. Everyone checks into trunk at least once a day.

14 Integration Integration early and often. Everyone checks into trunk at least once a day. Continuous Deployment Deploy as the final stage of continuous integration.

15 Integration Integration early and often. Everyone checks into trunk at least once a day. Deployment Deploy as the final stage of continuous integration. Continuous Delivery Software is always in a deployable state.

16 User Interface (Web, Swing) Business Analysts QA Domain Logic (Model) Application Server / Spring Persistance (OR Mapper) Firewall External Stuff Storage Application External Endpoints Mainframe Computer Modern software is complex!

17 Agile 101 "Agile" team Analysis + Design Development Centralized QA Integration + QA IT Operations Release and operation Customer Testing + Showcase Iteration The "last mile"

18 Continuous Delivery "Agile" team Analysis + Design Development Centralized QA Integration + QA IT Operations Release and operation Customer Testing + Showcase Iteration The "last mile" Customer Delivery team Constant flow of new features into production always business needs > operational constraints production ready

19 Potential Hindrances Lead time is too long Last mile is too painful Poor collaboration

20 Identify & remove friction

21 Continuous Integration Fast, automated feedback on the correctness of your application every time there is a change to code

22 Deployment Pipeline Fast, automated feedback on the production readiness of your application every time there is a change to code, infrastructure, or configuration production readiness 22

23 Deployment Pipelines

24 Prerequisites continuous integration comprehensive configuration management excellent automated testing at all levels

25 commit Stage Commit stage Version control source code commit tests build scripts Compile Unit test Assemble Code analysis deployable binaries test reports metadata Artifact repository Run against each check-in (continual integration) Starts building a release candidate If it fails, fix it immediately

26 Pipeline Construction commit functional test user acceptance test staging artifact respository artifact respository artifact respository artifact respository increasing confidence in production readiness Pipeline stages = feedback opportunities

27 UAT Stage Version control Artifact repository acceptance tests deployment scripts configuration data binaries Acceptance test stage Configure environment Deploy and smoke test Acceptance test Tear down test reports metadata Artifact repository End-to-end tests in production-like environment Triggered when upstream stage passes First DevOps-centric build 27

28 Manual Stage Version control Artifact repository deployment scripts configuration data binaries Later stages Configure environment Deploy and smoke test Tear down on request test reports metadata Artifact repository UAT, staging, integration, production, Push versus Pull model Deployments self-serviced through pushbutton process 28

29 Source code Env & app config Version control Env & app config Developers See code metrics and test failures Testers Self-service deployments UAT Configure environment Deploy binaries Smoke test Commit stage Compile Commit tests Assemble Code analysis Acceptance stage Configure environment Deploy binaries Smoke test Acceptance tests Capacity stage Configure environment Deploy binaries Smoke test Run capacity tests reports binaries metadata binaries reports metadata Operations perform push-button releases binaries Production Configure environment Deploy binaries Smoke test reports metadata Artifact repository 29

30 Machinery continuous integration ++

31

32

33

34

35

36

37 Increasing confidence in build's production readiness Environments become more production-like Commit stage Compile Unit test Analysis Build installers Acceptance test stage User acceptance testing Performance testing Production Faster feedback

38 chicken counting servers 0 1

39 Increasing confidence in build's production readiness Environments become more production-like Commit stage Compile Unit test Analysis Build installers Acceptance test stage User acceptance testing Performance testing Production Faster feedback

40 pipeline anti-patterns Increasing confidence in build's production readiness insufficient parallelization Environments become more production-like Commit stage Compile Unit test Analysis Build installers Acceptance test stage User acceptance testing Performance testing Production Faster feedback ideal time: < 10 minutes

41 pipeline anti-patterns Increasing confidence in build's production readiness insufficient parallelization Environments become more production-like Commit stage Compile Unit test Analysis Build installers Acceptance test stage User acceptance testing Performance testing Production Mingle: Faster feedback 3,282 test / 53 computers = ~1 hour

42 insufficient parallelization heuristic: make your pipeline wide, not long reduce the number of stages as much as possible parallelize each stage as much as you can create more stages if necessary to optimize feedback

43 pipeline anti-patterns inflexible workflow pipeline fans out as soon as it makes sense to do so

44 The Deming Cycle

45 The Scientific Method hypothesize experiment evaluate

46 principles of software delivery

47 principles automate almost everything build, deploy, test, release manual testing, approvals automatable high-value, humans only

48 principles keep everything you need to build, deploy, test, & release in version control requirements documents test scripts automated test cases network configuration scripts technical documentation database creation, upgrade, downgrade, and initialization scripts application stack configuration scripts libraries deployment scripts tool chains

49 When You Hire a New Developer

50 Infrastructure Consistency boxen.github.com

51 If it hurts... pain... do it more often bring the pain forward time principles

52 principles Cease dependence on mass inspection to achieve quality. Improve the process and build quality into the product in the first place build quality W. Edwards Deming in

53 continuous improvement Deming cycle principles

54 practices only build your binaries once

55 practices deploy the same way to every environment

56 practices smoke test your deployments

57 practices keep your environments similar

58 if anything fails, stop the line practices

59 Metrics & Monitoring

60 the driver for agile in the enterprise 21st century agility (business + IT) selling continuous delivery visibility risk mitigation responsiveness (cycle time)

61