Getting To Your Third Plugin
summary
Advice is concrete: try the Groovy plugin or jobs DSL plugin before writing an HPI, because small Groovy scripts at system level already disable failing jobs and enforce “keep 20 builds” at Netflix; an HPI is just a jar you can unzip to inspect jelly files; Stapler routes form posts to descriptors and databound constructors; expect ~111 extension points, ~600 plugins total, and oddities like readResolve and remote FilePath calls — use Maven first, migrate to Gradle later.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:58Disclaimer
- 2:52Why do we write plugins? An extendable open
- 3:48Don't write a plugin!
- 4:29Avoiding writing of plugins
- 4:44Groovy Plugin
- 6:52Display Object
- 7:17Groovy Postbuild Plugin
- 8:54Job DSL Plugin
- 9:55Getting Started
- 11:14Mental Model
- 14:44Extension Points
- 16:56What is a HPI?
- 18:38What is a Plugin?
- 19:13Plugin Model
- 19:48UI Model
- 22:24Descriptor Lifecycle
- 24:21Describable Lifecycle . Configuration - AJAX
- 26:36Stapler Example
- 27:15Break
- 29:20Jelly Sample
- 34:42Plugin Ecosystem
- 39:01Jenkins Singleton
- 41:04Jenkins Model
- 41:24Actions
- 42:09FilePath
- 42:58Build Tool
