Downloaded 225 times
Uploaded byThoughtworks
How do you implement Continuous Delivery? Part 3: All about Pipelines
This document discusses pipelines for continuous delivery. It describes how pipelines can incorporate progressive testing from unit tests to system integration tests. A typical pipeline includes stages for committing code, building, running unit tests, code analysis, and creating build artifacts. Deployment testing stages prepare environments, deploy artifacts, and run smoke and UI tests. Best practices are to keep everything in source control and replicate production. The document also discusses how to structure pipelines for multiple applications and federated systems.
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 YOU IMPLEMENT CONTINUOUS DELIVERY? Part3: All about Pipelines Share this ebook. PERSPECTIVES
- 2.
- 3. With CD, everybuild is a release candidate Pipeline for Progressive Testing
- 4. The Testing Pyramid Pipelinefor Progressive Testing Faster Feedback Broader Scope
- 5. The Testing Pyramid Pipelinefor Progressive Testing The Delivery Pipeline Faster Feedback Broader Scope Faster Feedback Increasing Confidence
- 6. The system beingdeveloped Pipeline for Progressive Testing Application A Application B Other Services
- 7. The system beingdeveloped Pipeline for Progressive Testing Application A Application B Other Services Unit Tests Each unit test covers one app component
- 8. The system beingdeveloped Pipeline for Progressive Testing Unit Tests Other components are stubbed Each unit test covers one app component
- 9. Pipeline for Progressive Testing UnitTests The first stage of the pipeline runs the unit tests
- 10. Pipeline for Progressive Testing Integrationtests cover a group of related components within the application Integration Tests
- 11. Pipeline for Progressive Testing Applicationtests cover an application running in a container, mocking connections to other applications Application Tests
- 12. Pipeline for Progressive Testing Systemtests cover the set of applications developed by the team, running together, mocking connections to external services System Tests
- 13. Pipeline for Progressive Testing Systemintegration tests exercise all parts of the system, including external dependencies System Integration Tests
- 14.
- 15. Application Pipeline Automated tests Automated tests Automated tests Tested Build Manual tests Live UnattendedProcess One-click deployments Pipeline Design Pattern Typical pipeline stages
- 16. Typical Commit Stage Commit Stage 1.Developer commits code to SCM Pipeline Design Pattern Typical pipeline stages
- 17. Typical Commit Stage Commit Stage 1.Developer commits code to SCM 2. Build server checks out & compiles code Pipeline Design Pattern Typical pipeline stages
- 18. Typical Commit Stage Commit Stage 1.Developer commits code to SCM 2. Build server checks out & compiles code 3. Unit tests Pipeline Design Pattern Typical pipeline stages
- 19. Typical Commit Stage Commit Stage 1.Developer commits code to SCM 2. Build server checks out & compiles code 3. Unit tests 4. Code analysis Pipeline Design Pattern Typical pipeline stages
- 20. Typical Commit Stage 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 Pipeline Design Pattern Typical pipeline stages
- 21. Pipeline Design Pattern Typical DeploymentTesting Stage Typical pipeline stages Deployment Testing Stage 1. Prepare environment
- 22. Pipeline Design Pattern Typical DeploymentTesting Stage Typical pipeline stages Deployment Testing Stage 1. Prepare environment 2. Retrieve artefact
- 23. Pipeline Design Pattern Typical DeploymentTesting Stage Typical pipeline stages Deployment Testing Stage 1. Prepare environment 2. Retrieve artefact 3. Deploy
- 24. Pipeline Design Pattern Typical DeploymentTesting Stage Typical pipeline stages Deployment Testing Stage 1. Prepare environment 2. Retrieve artefact 3. Deploy 4. Smoke Test
- 25. Pipeline Design Pattern Typical DeploymentTesting Stage Typical pipeline stages Deployment Testing Stage 1. Prepare environment 2. Retrieve artefact 3. Deploy 4. Smoke Test 5. Automated UI tests
- 26. Pipeline Design Pattern Other pipelinestages Typical pipeline stages Performance testing Security testing Exploratory testing User acceptance testing
- 27. Pipeline Design Pattern Best practicesfor pipeline stages Typical pipeline stages Keep everything in source control Only build artefacts once Replicate production constraints Deploy the same way every time Keep it simple, implement only those stages that make sense for your system
- 28. Pipeline Design Pattern Build Progression Typicalpipeline stages Pipeline progression 101
- 29. Pipeline Design Pattern Build Progression Typicalpipeline stages Pipeline progression r101 If tests fail, work stops until the issue is resolved
- 30. Pipeline Design Pattern Build Progression Typicalpipeline stages Pipeline progression r101 The fix is committed, and a new build goes through the pipeline from the beginning r102
- 31. Pipeline Design Pattern Build Progression Typicalpipeline stages Pipeline progression r101 Multiple builds may go through test without being deployed to production r102 r103
- 32. Pipeline Design Pattern Build Progression Typicalpipeline stages Pipeline progression r101 Deployment to production r102 r103 r104
- 33. Pipeline Design Pattern Joining multipleapplications Typical pipeline stages Pipeline progression Joining multiple applications Application A Application B Application Testing Complete Application Testing Complete
- 34. Pipeline Design Pattern Joining multipleapplications Typical pipeline stages Pipeline progression Joining multiple applications Application A Application B Application Testing Complete Application Testing Complete Integration Testing If tests fail for application A, application B can still proceed using the last “good” version of A LIVE
- 35. Pipeline Design Pattern Federated pipelines Typicalpipeline stages Pipeline progression Joining multiple applications Pre-release testing Provider Provider team could host instances for testing… Consumer
- 36. Pipeline Design Pattern Federated pipelines Typicalpipeline stages Pipeline progression Joining multiple applications Pre-release testing Provider Provider team could host instances for testing… Consumer LIVE Consumer contract tests …or provide packages for deployment by the Consumer team
- 37. AUTOMATED TESTING 37 Stay tunedfor part 4
- 38. LEARN MORE Deploy agreat product 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. Share this ebook. Visit our Continuous Delivery Channel for more posts like this.