Which of the core plugins was it that had this issue? I'm seeing this same
problem on my server.
On Monday, April 30, 2018 at 5:36:35 PM UTC-4 js78...@gmail.com wrote:
> I found the issue. It appears there is an update to one of the Jenkins
> core plugins that causes this if Jenkins itself is n
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.
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 caus
