Jenkins: Enabling Agility and Efficiency
summary
eBay and PayPal run Jenkins as the central PDLC engine for seven years, provisioning CI VMs via Mesos/Dockers, hooking GitHub pull requests into CI, and enforcing continuous integration, feedback and delivery. The stack runs unit, integration, security and performance tests (they target selective runs from ~10,000 tests), auto-merges or rejects PRs, and packages into environment-specific artifacts. Homegrown Jenkins plugins include an auto-merge/reject analyzer, a packaging plugin, a functional code-coverage agent, and an easy-config templating plugin.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 3:28Agenda
- 4:38Developer Life Cycle
- 8:25Developer Community
- 11:08Guiding Principles
- 13:26Execution Models
- 19:41Other Execution Model
- 26:08Build Analysis Test
- 26:34Build Systems Integration
- 28:17User Focus
- 29:59Thresholds
- 30:45Notification
- 33:09Automation
- 34:08Packaging
- 35:57System Test
- 38:22Functional Code Coverage
- 39:22Security
- 40:02EasyConfig
related talks
42mJenkins: Enabling Agility and Efficiency
35mJenkins Scaling and Organization for an Efficient CI
35mHow to Train Jenkins?
27mAutomation, Innovation and Continuous Delivery
50mJenkins in the Enterprise: Building Resilient CI Infrastructure
42mZero to Jenkins: Automatic builds + deploys
45mHow Builds and Delivers in the Cloud
33mJenkins 101