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.
Short answer, you need something like splunk or elastic search to parse the
logs and check for specific strings.
On Sun, Aug 11, 2019 at 5:55 PM Tony C wrote:
> Hi,
>
> I've been using Jenkins at work, for just over a year. I"m not the main
> architect of our groovy infrastructure. I'm just a us
Hi,
I've been using Jenkins at work, for just over a year. I"m not the main
architect of our groovy infrastructure. I'm just a user
who has several jobs which run each night.
Each of those jobs saves a handful of artifacts (log files) from that job.
I usually go into each job and look at a spec
