Hi Daniel, You were right, it was an archiveArtifacts step that was failing without any output whatsoever.
Thanks, Raj On Tuesday, January 3, 2017 at 12:22:07 PM UTC-8, Daniel Beland wrote: > > > I had a similar problem today and sadly my conclusion is it can be > anything. > > In my case the culprit was the archiveArtifacts that failed because it > couldn't find anything to archive. > It silently marked the build as failed without any output in the console > or the build pipeline steps page. > > Since the build was going on a bit after that it took me some time to find > it. > > My advice is to comment out as much as you can, running a build without > publishers and make sure it succeeds. > Then add publishers one at a time until you find the cause, assuming one > of them is the culprit. > > > On Wednesday, 28 December 2016 19:57:40 UTC-5, Raj Sahae wrote: >> >> Hi David, >> >> Here is a gist of the grepped failure output. I had to remove two >> segments of the output but I looked over them, very carefully, for any sort >> of failure indication and there was none. >> >> https://gist.github.com/rajsahae/743aed54f145bd664f65051082c622a5 >> >> The rest of the output, you can see, is largely some unit test reporting >> where it show 0 failures and 0 expected failures, but otherwise there are >> no error/failure indications. >> The command I used to produce this output was "grep -i -e fail -e error >> output.txt" where output.txt was a copy/paste of the full console output >> from my jenkins job. >> >> Thanks, >> Raj >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e964df9e-0ef9-499f-81d7-77ca168b9ace%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
