TDD for jenkins pipelines
summary
Built Groovy global shared libraries that standardize Jenkins pipelines for continuous delivery to Kubernetes, moving common deploy logic into reusable classes and Vars; initial brittle scripts break (jar vs war) and force a testing shift. Uses Gradle builds, Nexus for artifacts, mocks for Jenkins steps and a mocked HTTP client for unit tests, then runs unit + integration tests both locally and on Jenkins by passing Jenkins steps as constructor parameter. Result is reusable libraries loaded from Git, fewer broken deploys and growing community contributions.
AI-written summary · about
chapters (12)
- 0:00Introduction to CI/CD
- 1:20Legacy system challenges
- 3:24Moving to microservices
- 5:30Standardizing with Jenkins
- 7:41Fixing deployment mistakes
- 11:00Jenkins shared libraries
- 13:43Developing shared libraries
- 18:11Testing strategies
- 21:17Integration testing on Jenkins
- 23:20Live demo of testing
- 29:09Conclusion and results
- 32:34Q&A and resources
related talks
34mContinuous Delivery with Jenkins Workflow
52mContinuous Delivery of Microservices using Jenkins and Gradle
01h 29mBuilding a Continuous Delivery Pipeline with Gradle and Jenkins
04mContinuous Delivery with Jenkins' New Declarative Pipeline & Artifactory
54mAvoiding a Shared Library Nightmare
38mDeveloping and Validating Jenkins Pipelines
13mEvolution of containers in continuous integration
35mJenkins Scaling and Organization for an Efficient CI