In my current project, we use Jenkins to oversee our builds. Now they want me to write a Jenkins plugin to add some more monitoring options.
I looked at how the state monitoring plugin works, and I can’t understand some things. I tried to find documentation for writing a plugin, but it seems like this is really missing. (the site only mentions how to generate a basic project, and refers to a tutorial that is not informative)
What I'm trying to do is just add some options for each assembly, add a link and a monitoring page. Adding to the main page seems to be done by adding an action, but I'm still trying to figure out the rest. And how is all this related, for example:
Does hudson scan extension for class extension? (I don’t see the links anywhere in the notification, the monitoring plug-in class needs to be called somehow added to the main page)
Is the rootaction class the reason for URL binding, since you don’t mention it, enter the code here
And how the jelly files are linked to the correct page from the moment the mapping does not match. Or does Jenkins look at Bla folder names when you have a class called Bla extension RootAction?
Does anyone have pointers or a place where I can find decent documentation?
source
share