Or you can use the https://wiki.jenkins.io/display/JENKINS/Text-finder+Plugin <https://wiki.jenkins.io/display/JENKINS/Text-finder+Plugin> It provides already a way to grep files for a pattern and set the build status accordingly.
> Am 12.08.2019 um 06:49 schrieb 'Björn Pedersen' via Jenkins Users > <[email protected]>: > > Hi, > > I think the best solution would be to use warnings-ng and set up suitable > custom parser (I assume that none of the many available parsers fit your > use-case). Possibly in combination with the Build Failure Analyzer plugin > your jobs will show the correct status and where the errors happed. > > Björn > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/ccdab323-3894-4635-a06f-5f7a74c3b3ec%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-users/ccdab323-3894-4635-a06f-5f7a74c3b3ec%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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/3F83F7A5-5C3D-4786-8770-83B26B85DEC8%40gmail.com.
