obones/CruiseControl.NET — comment on commit 06b4b6578c48ea718379da9920d31d67a94e1e9e
File:  line 0
By obones:

Hello,

Yes, I saw the code for the dashboard but it stays in memory. If you
restart CCNet, it disappears.
And I want them to be in the integration properties so that I can use
them in the xsl that are used for the email publisher.
Right now, I can't use them.
We already discussed that a while back, please have a look at the issue.
I agree that my code might not be ideal, but there is a need to have the
failure tasks in the integration properties, just like one has the
failure users in there as well. And they are two different structures as
well, if I'm not mistaken.

RubenWillems wrote:
> the current code also has a way of detecting and displaying the failed tasks,
> see the live dashboard at http://build.nauck-it.de/ViewFarmReport.aspx
> currently the Fake project is broken, and you can see that the nant task failed.
>
> why the extra FailedTasks array?
> placing it into the integration properties is ok, but why an extra array?
> why not re-using the existing detection, or replace the existing detection with the new one
> having both is not ok, that's just asking for differences between the two
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/obones/CruiseControl.NET/commit/06b4b6578c48ea718379da9920d31d67a94e1e9e#commitcomment-879177
>
>