|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Having used this feature for a while now, it simply looks like solved and new errors are being reported inverse to what they should be.
The 'new' errors are listed in the view since the lastBuild tag. If there have been no new errors introduces since the last build, then there are no new errors displayed. But this is not logical, since the builds continue to be marked unstable because the error count exceeds the threshold, due to the errors introduced by the previous build.
The 'solved' errors are listed since the lastStableBuild tag. If errors have been solved between the current build and the last build, which might be unstable, then you can't see them, because the solved errors includes all errors solved since the last stable build.
What this ultimately means is that it is impossible to identify and fix new errors introduced between the last stable and the first unstable build, if the build history no longer exists. But you can see what errors have been resolved since the last stable build, which isn't much use. I'm not sure that I care what errors have been solved since the last stable build. What I want to see are the errors that have been introduced since the last stable build and what errors have been solved since the last build, so I know what errors I have left to resolve in order to restore the build to its original state.