Hi,

What's the current status of this plugin? Is there a timeline for the features in the TODO? It is someone currently working on any of them?

We intend to use this plugin exactly in the manner described in the plugin description. We want to display the status of the projects on a display, and when a build fails we want sound/flashing and extra information, like who is the last commiter for that project (the one responsible for the failed build).

We want to contribute on extending it with the features stated above.

Thanks.

Hi,

 I'd like to display an arbitrary lump of html (a pie chart) in each of the radiator job boxes.  How hard would this be to do?  Say if my judson job archive contained 'radview.html' it would be automatically placed in the radiator job box.

 I've upladed a jpg hashup to show the kind of thing that I mean.

Glenn

Hi,

 I'd like to display an arbitrary lump of html (a pie chart) in each of the radiator job boxes.  How hard would this be to do?  Say if my judson job archive contained 'radview.html' it would be automatically placed in the radiator job box.

 I've upladed a jpg hashup to show the kind of thing that I mean.

Glenn

Thanks for the plugin, it's really useful. We leave a screen in the office showing this page all the time.

However, to save electricity I wrote a simple webstart app called screenwaker that only turns the screen on if the builds are not passing. I try to justify it here ;)

Matt

Hi,

I did some modifications that increased the visibility of the builds. These modifications are:

• Black background -- Better contrast with build colors (red and green in my case)
• More opacity when the job is queue
• Heart beat when the job is building -- an animation like the building balls
• Build health icons

I wanna know how can I send these modifications to you, if you like to add them into the main project.

Thanks

Lucas

Thought I'd chime in with a tweak I made to main.jelly, and think this would be a great configurable option, which is to hide the Hudson header. We pull the Radiator view into a Confluence Wiki so business owners can view the status along with other build-related information and didn't need the header included. To hide the header, I added the following style after the meta refresh:

	<style type="text/css">
		#header{
			display:none;
		}
		#side-panel{
			display:none;
		}
		#view-message{
			display:none;
		}
		#main-panel{
			padding: 0px;
		}
	</style>

Hi Mark,

Have there been any thought to adding sounds to the changes that can be played on the console showing the radiator view?

Thanks!
Peter

I have a problem with icons in this plugin. It seems like they expect it to be on the root of the webserver, but Hudson is not necessary installed on the root of the webserver.

Should not image-links (and possibly other links) refer to <HUDSON_ROOT>/images/.... instead of /images/... ?

I would put this in as a bug, but when going to the issue tracker I see that there is not issues for this plugin and when trying to enter one I can only choose Hudson and not the plugin for Hudson.

Regards

Per A.

hi

I have installed radiator plug - in  version  1.7 and when I am trying to add some jobs to the view i receive 500 error code form server but if the view is empty I mean with no jobs, page is loaded with some comments like" job need to be added". I have been playing with versions from 1.7 to 1.2 and just version 1.2 works properly.

In every version different form 1.2 i received the same exception:

Exception:
Stacktrace:
org.apache.commons.jelly.JellyTagException: file:/opt/hudson2/plugins/radiatorviewplugin/WEB-INF/classes/hudson/model/RadiatorView/main.jelly:37:65:&nbsp; method sortFailing threw exception: tried to access field hudson.model.Result.ordinal from class hudson.model.ViewEntry
    at org.apache.commons.jelly.tags.core.InvokeTag.doTag(InvokeTag.java:109)
    at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
    at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
    at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
    at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:42)
    at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
    at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
    at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
    at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65)
    at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:112)

...

...

..

Does anyone has some idea what could cause this state. Isn't it related with some apache lib? My Hudson version is 1.327 and is working on Sun Solaris

BR

Matt

Is there a way / can an option be added to change the colours being used?

Awesome plugin though, thanks!

Hi,

How is managed the block size ? Especially red failing blocks which are too big: for example with 17 jobs, 1 failing, we got a very big red block and the stable ones are after the bottom of the page. Is it possible to reduce the red blocks size (there's currently a lot of unused space inside them) ?

Thanks

Would be nice if this plugin would display the page as a full-screen web-app on iOS devices. Created a JIRA issue for this request ( http://issues.jenkins-ci.org/browse/JENKINS-8981 ). Will look into adding this myself if I'll find some spare time.

The plugin server only shows version 1.9 at the moment under http://updates.jenkins-ci.org/download/plugins/radiatorviewplugin/

Additionally the latest link leads to "Not Found" page.

Hello,

I have a Jenkins CI with over 30 builds and when i choose the black background, it doesn't overlay all the builds.

Can this be modified or do i have to log a JIRA request ?

Regards.

Are there any plans to change the overall appearance of this plugin? The functionality of it looks great, but aesthetically... It could use some work.

I just upgraded to 1.13 and discovered that the claimed builds functionality seems to have changed?

The column that appeared at the right with claimed builds is not there any more. Is this by design or?

I just upgraded to 1.13 and discovered that the claimed builds functionality seems to have changed?

The column that appeared at the right with claimed builds is not there any more. Is this by design or?

Having a minor issue in version 1.13 with Firefox displaying the screen differently from other browsers (e.g. IE and Opera).

A job with failing tests should appear yellow; in Opera  or IE this is correct but in Firefox (which we use on our Radiator) the ".failing" class overrides the yellow background and we see the job coloured red instead. Equally a job that is unstable but for whatever reason has the successful class applied in css is coloured green in Firefox.

Disabling the style

.successful {
    background-image: -moz-linear-gradient(center bottom , #407A4B 5%, #008A2C 53%);
}

(or .failing equivalent) in the Element Inspector in Firefox fixes the problem temporarily.

Chris

<Edit> I wondered whether this was desired/intended behaviour, after re-reading the documentation above.  It seems claiming a broken build does indeed remove the red colour, and the build goes amber. 

However, when a build is successful but unstable (e.g. tests passing) my limited tests indicate that the Radiator shows the job in green. This is a bug, I think.

I've noticed that if you have a build in the radiator plugin that has not yet run, it appears Red (instead of Gray). Is this by design?

Part of our pipeline is to automatically create new jobs, so often times a radiator will have a job in it that has not yet run. Having this show up as a Failure is messing with people's heads!

Is there a way to customize the font colors and such?  For example the test failures are red on a red background.

Also, why do unstable jobs not show as orange?  They are showing as red.

Dan

Doesn't recurse folders.