Integrated Pipelines
summary
Pattern creates per-component CI pipelines and separate integrated pipelines that bank tested composite versions and push only when a common system test passes. Uses Jenkins plus Groovy to hide downstream jobs, Maven/Nexus or simple manifest files to record component versions (append/amend on integration), and job templating via disabled template jobs or export update reimport of job config XML through the Jenkins API. Scales to tens of components and handles many microservices and infrastructure-as-code pieces.
AI-written summary · about
chapters (8)
- 0:00Introduction to CI/CD
- 2:25Challenges in complexity
- 3:27Fat pipeline issues
- 4:49Integrated pipeline model
- 5:58Demonstration of workflow
- 7:21Technical implementation
- 8:48Scaling and templating
- 11:00Infrastructure as code
related talks
59mJenkins & continuous delivery pipeline
34mContinuous Delivery with Jenkins Workflow
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers
26mIntelligent Deployment Pipelines
29mFrom scheduled builds to commit triggered pipelines
45mBecoming a Plumber: Building Deployment Pipelines
48mInfrastructure-Agnostic Continuous Delivery
41mPipeline Patterns and Antipatterns - Things your Pipeline Should (Not) Do