[
https://issues.jenkins-ci.org/browse/JENKINS-12187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163211#comment-163211
]
Valerie Wagner commented on JENKINS-12187:
------------------------------------------
This new "feature" has broken our build. For various reasons, we run out tests
in one job but use a separate job for reporting/analysis. Now we cannot get any
reports because the job says that our testng xml files are too old (since they
are from an upstream build). Please make this feature optional in your next
release.
> If previous build has failed tests and next builds fails even before cleaning
> the workspace, the failed tests are shown as belonging to the next build, too
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-12187
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12187
> Project: Jenkins
> Issue Type: Bug
> Components: testng
> Reporter: kutzi
> Assignee: nalin_makar
> Priority: Minor
>
> We have a Maven build which failed in an pre-build step and therefore even
> reach the mvn clean goal.
> Because the previous, unstable build had failed tests, these tests were shown
> as belonging to the failed build - even thought the build didn't run any
> tests.
> This sound like a general problem in the plugin, because it scans the
> workspace for TestNG result files, so when the workspace is not cleared the
> old test results are naturally considered to be part of the new build.
> Maybe you still have an idea how this could be fixed
> Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
