Infrastructure-Agnostic Continuous Delivery
summary
Claim: Project piper codifies CI/CD best practices into ready-made pipelines and a step library as a binary so the same YAML config runs on Jenkins, GitHub Actions and (coming) Tekton. Evidence: SAP runs ~1,500 Jenkins instances, open-sourced piper end of 2017 and uses master internally; DORA numbers cited (200x+ deploys, ~2604x faster recovery, 7x lower failure rate). Built pieces: single config hierarchy, credentials via a neutral “world” path, GitOps decoupling; some Jenkins-only steps still pending.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:30About Me
- 2:44Elle performers - State of DevOps 2019
- 4:22Development Culture (according to DORA research)
- 8:25Shared codified knowledge ready to use
- 10:26Getting started
- 12:13Separation of pipeline logic and configuration
- 14:37Common configuration layer
- 17:57Example: Automatic versioning
- 24:19Scaling Continuous Delivery & DevOps...
- 27:43Project Piper evolution
- 29:31"Infrastructure-Agnostie" Continuous Delivery
- 33:45GitHub actions
- 36:29What's next?
related talks
29mContinuous Integration and Continuous Delivery Pipelines: Just the Basics
45mBecoming a Plumber: Building Deployment Pipelines
04mContinuous Delivery with Jenkins' New Declarative Pipeline & Artifactory
41mThe Pipeline-Driven Organization
40mIntegrated Pipeline for Private & Public Clouds w/Jenkins, &
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
26mIntelligent Deployment Pipelines
44mThe Pipeline Driven Organization|
