If we disabled these jobs, often we aren't interested anymore by their results
See http://wiki.jenkins-ci.org/display/JENKINS/Sectioned+View+Plugin for sample implementation
Reading the code, I'm just seeing that disable job shouldn't be displayed in the radiator view, but there is a bug. I will try fix it and to add the option
It's not bugged. It was added in version 1.7 which was released by olamy but not published on update center (I don't know why)
Patch to add an option to display or not deactivated jobs. Use grey background if they are displayed
I think the code will result in NPE when loading data from existing configuration, as the Boolean field is initialized to null.
I suggest either using boolean or handle the case where the field is null.
Ok . Thx for this feedback. It was clear for me how this sort of object was managed in hudson lifecycle.
I will fix it to ensure we don't initialize it with null.
I didn't understand why previous committers used Boolean objects instead of types. I looked at several plugins, but it seems there is no "official/recommended" usage of Objects vs types.
I'm using 1.444 with radiator plugin 1.13 and disabled projects do not appear in the Radiator view. I suggest closing this issue.
As mentioned in the previous comment, disabled jobs are not shown. So this bug is no longer relevant.