... after all, if they're green, they don't need to take up much screen space, do they? Imagine if they were all green. People would be just as happy (and just as informed) if it showed a big checkmark and nothing else. So you only really need to highlight the failing ones. Cradiator looks skinnable, and you're already using it, so that's the first thing I would try.
Radiator View (ideal for displaying on a screen on the office wall)
eXtreme Feedback Panel (even better than the Radiator View, especially for a FullHD flat panel)
Check out the other Build notifiers plugins for more ideas.
Personally, I have experienced the bunny, lava lamps, orbs and the radiator view. They all do the job but I have a little preference for the lava lamps. As Jeffrey mentioned in another answer, it's indeed funny to race against the wax to fix a build failure :)
We're currently using the Radiator View that includes now the modifications mentioned in this comment. It's use the space in a very neat way and does a perfect job, even when you have a lots of projects. It's just great.
Another idea, is to monitor multiple configuration sets and switch/fade between them at a set interval.
Our team has 12 projects to monitor, but to get around the clutter we currently have 1 machine with 2 monitors connected. Each monitor has an instance of Cradiator running on it. Doing this and using the RegEx Project Filter feature in Cradiator we show 5 projects on one monitor and a different 7 on the other. This should keep us going until about 15 projects, when the clutter will start to gang up on us again.
Cradiator is open source and the 'skin' concept is relatively isolated, just waiting for you to get your hands dirty in the source code!
In fact, I have just moved the source code for Cradiator to GitHub for a more flexible approach to sharing each other's work. Fork away.
One of the primary goals of radiating build status information into a room is to get developers to respond to broken builds and fix them. Quickly working out who might be responsible for a failing build is important.
What I have experienced first hand at my company is that processing check-in comments and displaying pictures of the users contributing to a build is very effective way of getting developers to react to build failures. People seem to respond to their face on a red bar, and others don't have to be so distracted.
With this in mind, I have developed a standalone build radiator web-app that talks to Jenkins and TeamCity over their REST APIs. CI-Eye is trivial to set up, and will probably give you better results in the workplace than many other plug-ins and radiator apps. 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.
If projects depend on each other somehow or if you can assign some priority (business value?), then I would consider some tree or a map kind of stuff. For 100+ projects it really should be more visible which greens/reds are more important than others. Myself I'm using just the structured web dashboard + systray. Not even email.
Brett, actually Cradiator just added a feature called MultiView to Cradiator - which is one way of fixing your problem of having too many projects showing.
So you can split your projects between separate "views". A view is the combination of URL/Skin & Project Filters.
Each view is shown on a rotation cycle every poll interval (default 30 seconds)
For example, if you have 12 projects, you can set 2 views which show only 6 each. See the Release Notes for v2.8 for details.
The show only breaking builds feature has been added as well.
发布评论
评论（7）
我使用 Hudson，当我有机会专门为其配备监视器时，我将从以下开始：
http://wiki.hudson-ci.org//download/attachments/37323554/Hudson_1.jpg
http://wiki.hudson-ci.org/display/HUDSON/Radiator+View+Plugin
...之后所有，如果它们是绿色的，就不需要占用太多屏幕空间，不是吗？想象一下，如果它们都是绿色的。如果它显示一个大复选标记而没有其他任何内容，人们也会同样高兴（并且同样了解情况）。所以你只需要突出显示失败的部分即可。 Cradiator 看起来可以换肤，而且您已经在使用它，所以这是我要尝试的第一件事。
I use Hudson, and when I have a chance to dedicate a monitor to it, I'm going to start with this:
http://wiki.hudson-ci.org//download/attachments/37323554/Hudson_1.jpg
http://wiki.hudson-ci.org/display/HUDSON/Radiator+View+Plugin
... after all, if they're green, they don't need to take up much screen space, do they? Imagine if they were all green. People would be just as happy (and just as informed) if it showed a big checkmark and nothing else. So you only really need to highlight the failing ones. Cradiator looks skinnable, and you're already using it, so that's the first thing I would try.
我在之前的回答中提到了 Hudson 的几种解决方案 :
我们当前使用的散热器视图现在包含 此评论。即使您有很多项目，它也能以非常整洁的方式利用空间并完成完美的工作。太棒了。
（来源：hudson-ci.org )
检查链接以获取更多屏幕截图。我有点怀念熔岩灯（因为它们很有趣），但在我看来，散热器视图提供了更好的反馈。
I mentioned several solutions for Hudson in a previous answer:
We're currently using the Radiator View that includes now the modifications mentioned in this comment. It's use the space in a very neat way and does a perfect job, even when you have a lots of projects. It's just great.
(source: hudson-ci.org)
Check the link for more screenshots. I miss lava lamps a bit (because they are fun) but the Radiator View provides better feedback IMO.
一个想法（Cradiator 确实有一个问题跟踪器项目）是仅显示损坏的构建 。
另一个想法是监视多个配置集并以设定的时间间隔在它们之间切换/淡入淡出。
我们的团队有 12 个项目需要监控，但为了避免混乱，我们目前有 1 台机器连接了 2 个监视器。每个监视器上都有一个运行的 Cradiator 实例。执行此操作并使用 Cradiator 中的 RegEx 项目过滤器 功能，我们在一台显示器上显示 5 个项目，在另一台显示器上显示不同的 7 个项目。这应该能让我们继续下去，直到大约 15 个项目，那时混乱将再次开始困扰我们。
Cradiator 是开源的，“皮肤”概念相对孤立，只等您亲自动手研究源代码！
事实上，我刚刚将 Cradiator 的源代码移至 GitHub，以便以更灵活的方式共享每个别人的工作。叉开。
One idea (and Cradiator does have an issue tracker item for it) is to only showing broken builds.
Another idea, is to monitor multiple configuration sets and switch/fade between them at a set interval.
Our team has 12 projects to monitor, but to get around the clutter we currently have 1 machine with 2 monitors connected. Each monitor has an instance of Cradiator running on it. Doing this and using the RegEx Project Filter feature in Cradiator we show 5 projects on one monitor and a different 7 on the other. This should keep us going until about 15 projects, when the clutter will start to gang up on us again.
Cradiator is open source and the 'skin' concept is relatively isolated, just waiting for you to get your hands dirty in the source code!
In fact, I have just moved the source code for Cradiator to GitHub for a more flexible approach to sharing each other's work. Fork away.
将构建状态信息辐射到房间的主要目标之一是让开发人员对损坏的构建做出响应并修复它们。快速找出谁可能对失败的构建负责非常重要。
我在公司的亲身经历是，处理签入评论和显示参与构建的用户的图片是让开发人员对构建失败做出反应的非常有效的方法。人们似乎会对红色条上的脸做出反应，而其他人不必如此分心。
考虑到这一点，我开发了一个独立的构建散热器 Web 应用程序，它通过 Jenkins 和 TeamCity 的 REST API 与它们进行通信。 CI-Eye 设置起来很简单，并且可能会比许多其他插件和散热器应用程序为您在工作场所提供更好的结果。尝试一下，让我知道你的想法——我正在积极改进它，并欢迎任何反馈。
CI-Eye 是免费且开源的 - 请参阅 CI-Eye wiki 了解更多详情。
One of the primary goals of radiating build status information into a room is to get developers to respond to broken builds and fix them. Quickly working out who might be responsible for a failing build is important.
What I have experienced first hand at my company is that processing check-in comments and displaying pictures of the users contributing to a build is very effective way of getting developers to react to build failures. People seem to respond to their face on a red bar, and others don't have to be so distracted.
With this in mind, I have developed a standalone build radiator web-app that talks to Jenkins and TeamCity over their REST APIs. CI-Eye is trivial to set up, and will probably give you better results in the workplace than many other plug-ins and radiator apps. 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.
持续集成散热器的一个不错的选择是 Buildron（Mac 和 Win）。
它支持同一屏幕中的许多构建，如您所见：
您可以使用远程控制（iOS 和 Android）。
A good option for continuous integration radiator is Buildron (Mac & Win).
Its supports a lot of builds in same screen, as you can see:
And you can filter builds using a remote control (iOS & Android).
如果项目以某种方式相互依赖，或者如果您可以分配一些优先级（商业价值？），那么我会考虑一些树或地图之类的东西。对于 100 多个项目，确实应该更明显地看出哪些绿色/红色比其他更重要。我自己只使用结构化网络仪表板+系统托盘。甚至没有电子邮件。
If projects depend on each other somehow or if you can assign some priority (business value?), then I would consider some tree or a map kind of stuff. For 100+ projects it really should be more visible which greens/reds are more important than others. Myself I'm using just the structured web dashboard + systray. Not even email.
Brett，实际上 Cradiator 刚刚向 Cradiator 添加了一项名为 MultiView 的功能 - 这是一个解决显示过多项目问题的方法。
因此，您可以将项目拆分为不同的“视图”。视图是 URL/Skin 和 URL/Skin 的组合。项目过滤器。
每个视图在每个轮询间隔（默认 30 秒）的轮换周期中显示。
例如，如果您有 12 个项目，则可以设置 2 个视图，每个视图仅显示 6 个。
有关详细信息，请参阅 v2.8 发行说明。
还添加了仅显示中断版本功能。
Brett, actually Cradiator just added a feature called MultiView to Cradiator - which is one way of fixing your problem of having too many projects showing.
So you can split your projects between separate "views". A view is the combination of URL/Skin & Project Filters.
Each view is shown on a rotation cycle every poll interval (default 30 seconds)
For example, if you have 12 projects, you can set 2 views which show only 6 each.
See the Release Notes for v2.8 for details.
The show only breaking builds feature has been added as well.