Getting Groovy with Jenkins
summary
Shows concrete Groovy snippets and a reproducible workflow: store scripts in source, one job called admin_update_pipeline_config pulls and archive artifacts, other jobs copy artifacts at build start. Uses system vs regular Groovy (system Groovy can reach the Jenkins API and can call system.exit), demonstrates the groovy post build plugin to add quick links and the email-ext plugin for customized failure emails, automates node reboots and build pinning, and reports that scripts survive routine Jenkins updates.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:26What is Groovy in Jenkins
- 2:40Customizing build pages
- 3:44System vs regular scripts
- 4:50Jenkins Groovy plugins
- 6:11Script storage best practices
- 8:24Executing scripts from source
- 10:17Accessing environment variables
- 12:00Handling variable differences
- 14:44Advanced environment variables
- 16:01Automating node administration
- 21:12Pinning builds for safety
- 22:25Creating and deleting nodes
- 23:41Customizing build page display
- 25:06Dynamic email notifications
- 27:30Dynamic script configuration
- 30:27Creating quick links
- 32:26Dynamic job display updates
- 33:43Leveraging Jenkins workspace
- 35:01Groovy label assignment
- 36:29Q&A and conclusion
related talks
46mWorkflow in Jenkins
43mSeven Habits of Highly Effective Jenkins Users
46mRemember the Build
42mSeven Habits of Highly Effective Jenkins Users
10mConfiguration as Code: The Job DSL Plugin
28mHiding in Plain Sight: Unmasking the Jenkins DSL
46mHow to Stop Clicking and Start Coding! THE Whole Jenkins as Code
44mGetting To Your Third Plugin