On my current project we're using Jenkins to monitor our builds. Now they want me to write a Jenkins plugin to add some more monitoring parameters.
I've taken a look at how the status monitor plugin works, and I can't figure some things out. I've tried to look for documentation for writing a plugin, but that seems to be sorely lacking. (the site only mentions how to generate the base project, and refers to a tutorial that's not that informative)
What I'm trying to do is just add some options to each build, add a link, and a monitoring page. Adding to the main page is apparently done by adding the action, but I'm still trying to figure out the rest. And how it all ties in, such as:
Does hudson scan for class extending notifier? (I can see no references anywhere to the notifier class of the monitoring plugin yet it must be called somehow since it is added to the main page)
Does the rootaction class cause the URL binding since there also seem to be no references to that enter code here
And how does jelly files get bound to the correct page since the mapping do not match. Or does Jenkins scan for a folder names Bla when you have a class called Bla extending RootAction?
Does anyone have any pointers, or a place where I can find some decent documentation?
I've seen people use a tutorial I found here to make plug-ins for Hudson. Jenkins wasn't forked all that long ago, so it should be mostly the same - you'd just need to account for the changed repositories.
Helpful videos:
- 2013-06-15 Jenkins Hackathon -- Introduction zu Plugin Development by Kohsuke Kawaguchi have a lot of information about finding docs, getting started, debugging and testing plugins. Must see video!
- 2012 San Fran JUC: Justin Ryan - Getting To Your Third Plugin good explain of how to build structure of plugins, what is descriptors and describable.
- http://cleantestcode.wordpress.com/2013/11/03/how-to-write-a-jenkins-plugin-introduction/ - cycle of 4 posts about writing UI-extend plugin.
来源：https://stackoverflow.com/questions/5531729/writing-jenkins-plugin-where-is-the-documentation