Take Control. Write a Plugin. Part II
summary
Shows a concrete plugin (a notifier that appends a configurable message when a build fails) and how it actually works end to end: remote execution uses Callable via Java serialization sent over a Channel; remote file handling uses FilePath/FileCallable and Launcher to run processes so platform quirks (slashes, quoting, POSIX vs DOS permissions) are handled correctly; UI uses Groovy taglib and debuggable UI instead of Jelly; refactoring keeps old configs alive via XStream aliasing registered with an initializer.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:36JFrog & Jenkins
- 2:22First, let's vote
- 3:29Overview - Why plugins
- 4:06What can I extend?
- 5:15Environment
- 5:43The "Motivation" Plugin
- 11:26Working with remote agents
- 12:09Closure
- 13:32Cast your bread on the waters
- 13:44Channel
- 14:27Distribution Abstractions - FilePath
- 16:21Distribution Abstractions - Launcher
- 18:13Working in multiple Oss
- 19:26Running script...
- 19:47Can You Spot The Error?
- 22:57Permissions Dance
- 26:37Creating Ul using Groovy
- 30:18Writing custom Jelly(?) tags
- 30:34Writing custom Helly Groovy tags
- 30:511. Implement
- 32:012. Use!
- 33:06Maintaining backwards compatibility
- 34:52Refactoring!
related talks
51mGradle Plugin, Take Control of the Build!
17mEasy Build Plugins With Mill
01h 52mPlugins Training Workshop
21mMake Gradle work for you, create your own tasks and plugins
33mUnderstanding Gradle and writing your own Gradle Plugin
26mBackstage Plugin Development: Tales from the Trenches
01h 03mPower of Gradle
01h 15mKeeping growing software projects under control with Gradle