Question

I'm continuing to have issues with the issue I've described here: Jenkins fails ALL THE TIME with hudson.util.IOException2, and another user has described here: Jenkins/Hudson SVN Issue

Jenkins recently updated their SVN plugin to retry on this error 10 times; while this tends to work, it still fails on each job at least once every 2 days or so, sending emails to everybody that the build failed. All that usually needs to happen to fix the problem is re-run the build and everything works.

Is there a way (perhaps a plugin or some sort of setting) to make Jenkins completely IGNORE all build failures where the line: hudson.util.IOException2: revision check failed is in the logs? This would make things a lot nicer for everybody and reduce the number of false alarms that a build is broken.

Was it helpful?

Solution

Yes, use the Jenkins text finder plugin to mark the build successful if you find the IOException error message.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top