Using Jenkins Optimally in Feature-Branch Development
summary
How to build a Jenkins pipeline-based workflow for feature-branch development using the Pipeline plugin and a shared pipeline library on minikube/Docker. The setup auto-creates a job per feature branch, runs lint/tests/coverage in parallel, builds Docker images to a registry and deploys each branch to its own dynamic port range; the develop branch triggers automated releases and release-note generation from issue IDs, deployments use locks to avoid collisions, and interrupted pipelines can resume after Jenkins restarts (demo noted some flaky plugins and network issues requiring occasional manual cleanup).
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:30Demo setup
- 5:56Hello-World demo
- 9:17Unit tests in pipeline
- 15:00Feature-branch pipeline
- 16:51Jenkins plugins & multi-branch
- 21:57Jenkinsfile syntax
- 27:16Workspace & parallel jobs
- 32:14Pipeline libraries
- 39:54Summary
- 42:41Q&A
related talks
36mUsing Jenkins to Build, Deploy, and Automate Projects
48mPre-Tested Integration in Jenkins Using a "Branchy Approach"
30mContinuous Integration; Tips & Tricks
06mBuilding Continuous Delivery Pipelines
13mEvolution of containers in continuous integration
39mRemove your Testing Bottleneck with CI/CD Pipelines
42mZero to Jenkins: Automatic builds + deploys
29mFrom scheduled builds to commit triggered pipelines