[JIRA] (JENKINS-12436) Log parser plugin should not store the absolute path to the parsing file in each job config

jed.jacobs@prudential.com (JIRA)

unread,

Mar 7, 2019, 10:51:05 AM3/7/19

to jenkinsc...@googlegroups.com

Jed Jacobs commented on

JENKINS-12436

Re: Log parser plugin should not store the absolute path to the parsing file in each job config

Why is this still unresolved? We have to open and save hundreds of configurations so the log parsing file could be found in its new location on the server.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

mark.earl.waite@gmail.com (JIRA)

unread,

Mar 7, 2019, 11:44:02 AM3/7/19

to jenkinsc...@googlegroups.com

Mark Waite commented on

JENKINS-12436

Re: Log parser plugin should not store the absolute path to the parsing file in each job config

Jed Jacobs it is not resolved because no one has submitted a pull request to propose a fix. The last commit to the plugin GitHub repository was over 3 years ago.

You might consider using the "Adopt a plugin" instructions to adopt the log parser plugin.

You could create one or more tests that show the problem, then make the code change that fixes the tests, then confirm that the fix works in regular working environments.

Plugin maintenance is not actually a lot of effort for smaller plugins like this one and it can help you and help others in the community.