|
||||||||
|
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.
I have a build at the moment with 1 stable build and 9 subsequent unstable builds because the errors haven't yet been resolved. If another build is triggered, the build history for the first unstable build will be lost and we lose the information about the new errors introduced by that build. The delta for the other 8 builds is 0, so there is no information about new errors. The only way to then resolve the "new" errors is to download the cppcheck.xml file from the stable build we have, download the second copy from the last build we have and diff them. This then shows us the new errors introduced since the last stable build, so that we can fix them and move on.