Downloaded 117 times
Uploaded byThoughtWorks Studios
How do you implement Continuous Delivery? Part 3: All about Pipelines
The document discusses the implementation of continuous delivery (CD) through a structured pipeline approach that emphasizes progressive testing at multiple stages, including unit tests, integration tests, and system tests. It outlines best practices for pipeline design, such as keeping everything in source control and deploying consistently, while also addressing the coordination of multiple applications within a single pipeline. The content culminates in a call to action for utilizing tools to facilitate efficient continuous delivery processes.
More Related Content
Similar to How do you implement Continuous Delivery? Part 3: All about Pipelines
How do you implement Continuous Delivery? Part 3: All about Pipelines
- 1. How do youimplement Continuous Delivery? Part 3: All about Pipelines
- 2.
- 3. With CD, everybuild is a release candidatePipeline for progressive testing þ þý ý þ þ ý þ þ
- 4.
- 5. The Testing Pyramid Pipeline for progressive testing TheDelivery Pipeline Faster Feedback Broader Scope Faster Feedback Increasing Confidence
- 6. The system beingdevelopedPipeline for progressive testing Other Services Application A Application B
- 7. Pipeline for progressive testing Unit Tests Eachunit test covers one app component Other components are stubbed
- 8. Pipeline for progressive testing The firststage of the pipeline runs the unit tests Unit Tests
- 9. Pipeline for progressive testing Integration Tests Integrationtests cover a group of related components within the application
- 10. Pipeline for progressive testing Application Tests Applicationtests cover an application running in a container, mocking connections to other applications
- 11. Pipeline for progressive testing System Tests Systemtests cover the set of applications developed by the team, running together, mocking connections to external services
- 12. Pipeline for progressive testing System Integration Tests Systems integrationtests exercise all parts of the system, including external dependencies
- 13.
- 14. Pipeline Design Patterns Application Pipeline Automated tests Automated tests Automated tests Tested Build Manual testsLive Unattended Process One-click deployments Typical Pipeline Stages
- 15. Pipeline Design Patterns Typical CommitStage Commit Stage 1. Developer commits code to SCM Typical Pipeline Stages
- 16. Pipeline Design Patterns Typical CommitStage Commit Stage 1. Developer commits code to SCM 2. Build server checks out & compiles code Typical Pipeline Stages
- 17. Pipeline Design Patterns Typical CommitStage Commit Stage 1. Developer commits code to SCM 2. Build server checks out & compiles code 3. Unit tests Typical Pipeline Stages
- 18. Pipeline Design Patterns Typical CommitStage Commit Stage 1. Developer commits code to SCM 2. Build server checks out & compiles code 3. Unit tests 4. Code analysis Typical Pipeline Stages
- 19. Pipeline Design Patterns Typical CommitStage Commit Stage 1. Developer commits code to SCM 2. Build server checks out & compiles code 3. Unit tests 4. Code analysis 5. Create build artefact Typical Pipeline Stages
- 20. Pipeline Design Patterns Typical DeploymentTesting Stage Deployment Testing Stage 1. Prepare environment Typical Pipeline Stages
- 21. Pipeline Design Patterns Typical DeploymentTesting Stage Deployment Testing Stage 1. Prepare environment 2. Retrieve artefact Typical Pipeline Stages
- 22. Pipeline Design Patterns Typical DeploymentTesting Stage Deployment Testing Stage 1. Prepare environment 2. Retrieve artefact 3. Deploy Typical Pipeline Stages
- 23. Pipeline Design Patterns Typical DeploymentTesting Stage Deployment Testing Stage 1. Prepare environment 2. Retrieve artefact 3. Deploy 4. Smoke Test
- 24. Pipeline Design Patterns Typical DeploymentTesting Stage Deployment Testing Stage 1. Prepare environment 2. Retrieve artefact 3. Deploy 4. Smoke Test 5. Automated UI tests Typical Pipeline Stages
- 25. Pipeline Design Patterns Other pipelinestages q Performance testing q Security testing q Exploratory testing q User acceptance testing Typical Pipeline Stages
- 26. Best practices forpipeline stages Keep everything in source control Only build artefacts once Replicate production constraints Deploy the same way every time Pipeline Design Patterns Typical Pipeline Stages Keep it simple, implement only those stages that make sense for your system
- 27. Pipeline Design Patterns Build Progression þþ þr101 Typical Pipeline Stages Pipeline Progression
- 28. Pipeline Design Patterns Build Progression þþ þr101 ý If tests fail, work stops until the issue is resolved Typical Pipeline Stages Pipeline Progression
- 29. Pipeline Design Patterns Build Progression þþ þr101 ý The fix is committed, and a new build goes through the pipeline from the beginning þ þr102 þ þ Typical Pipeline Stages Pipeline Progression
- 30. Pipeline Design Patterns Build Progression þþ þr101 ý Multiple builds may go through test without being deployed to production þ þr102 þ þ þ þr103 þ þ Typical Pipeline Stages Pipeline Progression
- 31. Pipeline Design Patterns Build Progression þþ þr101 ý Deployment to Production þ þr102 þ þ þ þr103 þ þ þ þr104 þ þ þ þ Typical Pipeline Stages Pipeline Progression
- 32. Joining multiple applications Pipeline DesignPatterns Application A Application B Typical Pipeline Stages Pipeline Progression Joining multiple applications
- 33. Pipeline Design Patterns Application A ApplicationB Application Testing Complete Application Testing Complete Joining multiple applications Typical Pipeline Stages Pipeline Progression Joining multiple applications
- 34. Pipeline Design Patterns Application A ApplicationB Application Testing Complete Application Testing Complete Integration Testing Joining multiple applications If tests fail for application A, application B can still proceed using the last “good” version of A Typical Pipeline Stages Pipeline Progression Joining multiple applications LIVE
- 35. Pipeline Design Patterns Provider Consumer Federated Pipelines Pre-release testing TypicalPipeline Stages Pipeline Progression Joining multiple applications Provider team could host instances for testing…
- 36. Pipeline Design Patterns Provider Consumer Federated Pipelines Pre-release testingLIVE Consumer contract tests …or provide packages for deployment by the Consumer teamTypical Pipeline Stages Pipeline Progression Joining multiple applications Provider team could host instances for testing…
- 37. Automated Testing Stay tunedfor Part 4…
- 38. Deploy a greatproduct faster. Agile teams deliver working software early and often. Go automates and streamlines the build-test-release cycle for worry-free, continuous delivery of your product. Learn More See how Go can help you in your CD journeygo Continuous Delivery