I found the issue. It appears there is an update to one of the Jenkins core plugins that causes this if Jenkins itself is not updated to the latest LTS release. in my case I cannot update to the latest because the upgrade is failing and I have not had a chance to debug thru to find that cause. I also was unable to determine exactly which core plugin causes this issue. For now I just had to disable the log parser on this build server.
On Wednesday, April 25, 2018 at 11:20:01 AM UTC-7, js78...@gmail.com wrote: > > In the last two days the Log Parser plugin has started marking some builds > as Aborted. I have nothing in my parser config to mark it for Aborted or > look for aborted in any way. > This plugin has not been updated in years so this seems to be another > update in some other part of Jenkins that is causing this. > The only place the word Aborted even appears in the log is when the Log > Parser runs and sets the status to Aborted: > *Build step 'Console output (build log) parsing' changed build result to > ABORTED* > it also ends up not producing any Parsed Console output. > > Has anyone else experienced this? Any solution other than removing the > plugin? > > > > > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/aec3678d-7a0c-4e80-8f45-330fed44850f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
