编写 jenkins 插件：文档在哪里？
在我当前的项目中，我们使用 Jenkins 来监控我们的构建。现在他们想让我写一个 Jenkins 插件来添加更多的监控参数。
我已经研究了状态监视器插件的工作原理，但我无法弄清楚一些事情。我试图寻找编写插件的文档，但似乎非常缺乏。 （该网站仅提到如何生成基础项目，并引用了一个内容不丰富的教程）
我想做的只是向每个构建添加一些选项，添加一个链接和一个监视页面。添加到主页显然是通过添加操作来完成的，但我仍在尝试弄清楚其余的事情。以及它们是如何联系在一起的，例如：
Hudson 是否扫描类扩展通知程序？ （我看不出 对通知者的任何地方的引用 监控插件的类还没有 必须以某种方式调用它，因为它 添加到主页）
rootaction类是否导致 URL 绑定似乎也有 没有提及那个 在此处输入代码
果冻文件如何绑定 到正确的页面，因为 映射不匹配。或者确实 Jenkins 扫描名为 Bla 的文件夹 当你有一门名为 Bla 的课程时 扩展 RootAction？
有人有任何指示，或者我可以找到一些像样的文档的地方吗？
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 hereAnd 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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我看到人们使用我在此处找到的教程 为 Hudson 制作插件。 Jenkins 很久以前就没有分叉，所以它应该基本相同 - 你只需要考虑更改的存储库。
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: