Continuous Delivery with Jenkins Workflow
summary
Jenkins Pipeline (Groovy) is used to replace many Jenkins jobs with a few multibranch pipelines and shared pipeline libraries (example helper waitForUrl) to factor common steps and target 5–10 minute feedback. Docker images run reproducible integration suites, Ansible playbooks handle provisioning, and UI tests are integrated into the pipeline via step classes, screenshots and CSV-driven data so a failing UI test produces an attachable ticket; overall code size is reduced (end tests around ~20 Java lines).
AI-written summary · about
chapters (11)
- 0:00Continuous Delivery basics
- 1:28What is Continuous Delivery?
- 3:33Jenkins Pipeline concept
- 7:08Jenkins Pipeline benefits
- 11:49Pipeline script syntax
- 17:33Ansible in pipeline
- 21:29Pipeline libraries
- 23:56Serenity BDD UI tests
- 28:33Tools and best practices
- 30:21Summary
- 30:54Q&A
related talks
04mContinuous Delivery with Jenkins' New Declarative Pipeline & Artifactory
48mWorkflow in Jenkins
34mTDD for jenkins pipelines
52mContinuous Delivery of Microservices using Jenkins and Gradle
46mWorkflow in Jenkins
27mAutomation, Innovation and Continuous Delivery
46mWorkflow in Jenkins
13mEvolution of containers in continuous integration
