Hi there, in case you ever tried to find out why your Gerrit patch failed on Jenkins, you're probably familiar with the long console output each job produces, and how not-straight-forward it is to find the part you're looking for.
Today I installed and configured the Log Parser plugin which looks for user-defined patterns in the console log and collects any occurrences. So far, I configured javac warnings and errors. You can see it in action: - [1] is a failing patch (Damn!) - [2] is the build that failed. You can already see the new text that says "2 errors, 604 warnings". - If you click on "Parsed Console Output" in the left menu (or here: [3]) you can either click on the labels to the left to see all matches, or scroll through the highlighted console output on the right. Happy debugging, Franz [1] http://saros-build.imp.fu-berlin.de/gerrit/#/c/3159/ [2] http://saros-build.imp.fu-berlin.de/jenkins/job/Saros-Full-Gerrit/213/ [3] http://saros-build.imp.fu-berlin.de/jenkins/job/Saros-Full-Gerrit/213/parsed_console/ ------------------------------------------------------------------------------ _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
