我可以在 Hudson/Jenkins 中配置散热器视图吗？
我的团队使用 Radiator View 插件来实现 Jenkins 用于快速反馈一些不同项目的构建状态。我们讨论过的一件事会很有帮助，那就是 SVN 修订号是否包含在此视图中。经过快速谷歌搜索后，我还没有找到关于这个插件是否可配置的明确答案；有谁知道是否有一种简单的方法来添加此信息？
My team uses the Radiator View plugin for Jenkins for fast feedback on the build status of a few different projects. One thing we discussed that would be helpful is if the SVN revision number were included in this view. After only a quick Google search, I haven't found a clear answer on whether this plugin is configurable or not; does anyone know if there's a straightforward way to add this information?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我不认为那里有可定制的数字，但你可以做的是，拉下源代码并获取所有失败版本的修订号，你必须自己编写代码，但从我看来，没有办法使用配置选项执行此操作。
如果您只需要获取该信息，您可能想要尝试的是最近损坏的构建的构建页面上的最新更改。
祝你好运。
I dont think there are customizable figures there but what you can do is, pull down the source and get the revsion numbers for all the failing builds, you will have to write the code yourself, but from what I can see there is no way of doing this with the configuration options.
What you might want to try if you just need to get that information is the recent changes on the build page of the recently broken build.
Goodluck.
我能问为什么显示 svn 修订号会有帮助吗？据我了解，建筑散热器应该将有意义的信息“辐射”到房间中。 svn 编号毫无意义，除非您可以在存储库中查找该编号，在这种情况下，您无论如何都可以在 Jenkins 上查找修订号。
我只是猜测，如果我错了，请纠正我，但我怀疑您真正的愿望是有某种方法快速找出谁可能对失败的构建负责。如果是这种情况，那么处理签入评论并显示相关用户的图片是让开发人员对失败的构建做出反应的更有效方法。我在公司亲身经历过这一点。
考虑到这一点，我开发了一个独立的构建散热器 Web 应用程序，通过其 REST API 与 Jenkins 进行通信。 CI-Eye 设置起来很简单，并且可能会在工作场所为您提供比 Radiator View 插件更好的结果。尝试一下，让我知道你的想法——我正在积极改进它，并欢迎任何反馈。
CI-Eye 是免费且开源的 - 请参阅 CI-Eye wiki 了解更多详情。
Can I ask why it would be helpful to have the svn revision number on display? As far as I understand it, a build radiator is supposed to 'radiate' meaningful information into the room. The svn number is fairly meaningless unless you can look up the number in the repository, in which case you could have just looked up the revision number on Jenkins anyway.
I'm just guessing, and do correct me if I'm wrong, but I suspect that your real desire is to have some way of quickly working out who might be responsible for a failing build. If this is the case, then processing check-in comments and displaying pictures of the users involved is a far more effective way of getting developers to react to failing builds. I've experienced this first hand at my company.
With this in mind, I have developed a standalone build radiator webapp that talks to Jenkins over its REST API. CI-Eye is trivial to set up, and will probably give you better results in the workplace than the Radiator View plug-in. Give it a try, and let me know what you think -- I'm quite actively improving it, and welcome any feedback.
CI-Eye is free and open source -- see the CI-Eye wiki for more details.