I fixed core-integration-testing-maven-3-embedded job (since wiping out the workspace was not sufficient because this target was re- appearing and rat complained, I just ran a build with -Drat.skip)
Other Maven 3 jobs are failing for other cause [1], I did not investigate Regards, Hervé [1] https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3-jdk-1.7/1926/console Le samedi 17 décembre 2016, 04:17:42 CET Christian Schulte a écrit : > Hi, > > I renamed the 'maven-aether-provider' module to > 'maven-resolver-provider'. What happens on Jenkins is this: The > 'maven-aether-provider' folder will not get deleted correctly when > Jenkins performs the SCM update/checkout. This may be due to the > existence of the 'maven-aether-provider/target' folder. We cannot run a > post-build 'clean' execution. This would throw away the build result > after a successfull build so that no-one could download anything of that > build result. Does someone know how to make Jenkins correctly handle > module renames? Issue is the old module folder is lying around on every > build node and the workspace needs to be deleted manually on every build > node. That's one of the reasons Jenkins is sending out failure notices > for the 'maven-3.x' and related build jobs since a few days. Can we do > something about it? If not, just delete the workspace whenever such a > build failure gets reported until all build nodes caught up. > > Regards, --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
