Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
For Issue 50 #61
the current code also has a way of detecting and displaying the failed tasks,
why the extra FailedTasks array?
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: 06b4b65#commitcomment-879177
Well, I tried that, but it's not that easy as it is implemented as "messages", just like the list of breakers you see in the front page of the dashboard.
In memory for the summary on the dashboard
If I were to remove the in memory implementation for failed tasks, then maybe I should remove the in memory implementation for failure users and I'm not sure this is desirable as it might have consequences on other parts of the application (CCTray?)
added a commit
this pull request
Jan 26, 2012
maybe it was merged out again?