Olaf Bergner commented on Bug JENKINS-9757

We've been bitten by this, too, and I'm afraid that wiping the workspace prior to building - either by executing maven's "clean" phase or using Jenkins' support for doing so - is no solution for us. We use maven's incremental build plugin to greatly speed up our builds, and this does obviously not work when previously compiled class files are erased. So we at least desperately need a fix.

What annoys me personally most about this issue is the inordinate amount of time it took me to track our build's failing to this root cause. There is nothing - neither on Jenkins job page proper nor in the console output - to clearly tell a user what made Jenkins fail the build. I strongly suggest to adopt a policy of always clearly and prominently publishing why a certain build failed. Sending users on a wild goose chase is, well, impolite.

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

Reply via email to