[JIRA] (JENKINS-12436) Log parser plugin should not store the absolute path to the parsing file in each job config
Title: Message Title Martin Reinhardt updated an issue Jenkins / JENKINS-12436 Log parser plugin should not store the absolute path to the parsing file in each job config Change By: Martin Reinhardt Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142802.1326840022000.13677.1562012640947%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12436) Log parser plugin should not store the absolute path to the parsing file in each job config
Title: Message Title Martin Reinhardt commented on JENKINS-12436 Re: Log parser plugin should not store the absolute path to the parsing file in each job config any PR is welcome Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142802.1326840022000.13688.1562012641107%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12436) Log parser plugin should not store the absolute path to the parsing file in each job config
Title: Message Title 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12436) Log parser plugin should not store the absolute path to the parsing file in each job config
Title: Message Title 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) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12436) Log parser plugin should not store the absolute path to the parsing file in each job config
Kamil Kisiel commented on JENKINS-12436 Log parser plugin should not store the absolute path to the parsing file in each job config I should add, in order to fix the job configurations it was sufficient to go to each job and click the "save" button. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12436) Log parser plugin should not store the absolute path to the parsing file in each job config
Kamil Kisiel commented on JENKINS-12436 Log parser plugin should not store the absolute path to the parsing file in each job config I just got bit by this rather badly. We moved our console log parsing file on the filesystem and updated the global jenkins configuration. I assumed since the rules are chosen by name in the job config they would all be updated automatically (after all, isn't that the point of a global config?). Of course it didn't and even worse the error is not reported anywhere in the job console and doesn't cause the job to fail in any way. The only way to discover the problem was the browse to a job and check its parsed console log output which displayed the message: ERROR:Failed to parse console log : log-parser plugin ERROR: Cannot parse log: Can't read parsing rules file: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
