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

[ka...@kamilkisiel.net (JIRA)]

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