Hiding in Plain Sight: Unmasking the Jenkins DSL
summary
Argues that the true Jenkins DSL is the form-submission JSON exposed as structured form submission and that converting it to YAML with the yaml project plugin gives versioned job config that works with existing plugins rather than reimplementing them. Demos create jobs from YAML, convert UI-created freestyle and matrix jobs to YAML, and use the multi-branch plugin to auto-discover branches and instantiate builds. Claims plugin count (>1,000) makes bespoke DSL support impractical and reports success: configs versioned with code and most server config moved out of master.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:18What is a DSL
- 3:20Google’s CI/CD DSLs
- 5:25Pitfalls of Jenkins DSLs
- 7:32How the new DSL works
- 11:05YAML plugin demo
- 14:01Syntactic sugar in DSL
- 16:27UI to YAML conversion
- 19:40Demo recap and next steps
- 20:46Multi-branch projects
- 24:04Multi-branch YAML demo
- 26:39Advanced YAML filtering
- 27:42Q&A
related talks
28mHiding in Plain Sight: Unmasking the Jenkins DSL
10mConfiguration as Code: The Job DSL Plugin
51mJenkins Configuration as Code - Automate your automation Server
38mUsing Jenkins Job Builder to Easily Manage Your Jobs
33mJenkins 101
36mDealing with Data Driven Test Combinatorial Complexity using Jenkins Job DSL
01h 01mOpening Keynote
54mKeynote Address and Opening Remarks