Pre-Tested Integration in Jenkins Using a "Branchy Approach"
summary
A Jenkins plugin (originating from the ClearCase UCM work) automates a pre-tested integration flow that runs every commit through the pipeline, integrates branches named by convention into master, runs unit/static/full test gates (Atmel runs a one‑hour Jaguar Land Rover suite), and auto‑commits or discards the change and deletes the ready branch on success. It enforces squash commits (no fast‑forward) so each delivery appears as a single identifiable commit and supports promotion branches (master→stable→release).
AI-written summary · about
chapters (20)
- 0:00Praqma introduction
- 1:20Pre-tested integration plugin origin
- 3:48Joint Open Source Roadmap Alliance
- 5:58Continuous delivery pipeline
- 8:51Release candidate concept
- 10:14Toll gate principle
- 11:20Branchy approach for integration
- 13:08Git Flow problems
- 15:17Three branch types
- 17:21Ten branching principles
- 21:40Automating promotion branches
- 23:04Balancing freedom and quality
- 25:55Git plugin setup
- 27:21Local branch collaboration
- 29:09Squashing commits
- 31:58Merge strategies differences
- 38:24When to squash commits
- 40:09Plugin live demo
- 46:07Praqma tooling support
- 47:02Q&A
related talks
48mUsing Jenkins Optimally in Feature-Branch Development
36mUsing Jenkins to Build, Deploy, and Automate Projects
29mFrom scheduled builds to commit triggered pipelines
39mRemove your Testing Bottleneck with CI/CD Pipelines
34mContinuous Delivery with Jenkins Workflow
30mImplementing Continuous Deployment with Jenkins & Gerritt
42mZero to Jenkins: Automatic builds + deploys
42mJenkins: Enabling Agility and Efficiency