|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
Hi,
I'm one of the maintainers of the JobConfigHistory plugin. We weren't aware of the problem, I only found this issue by chance.
However, we could add a configuration option that allows you to have changes made by the system user ignored by the config history. This would be relatively easy to implement, but means that changes made by the system user will get attributed to the user who makes the next config change. If this would be a solution for your problem, please open an issue at
https://issues.jenkins-ci.org/browse/JENKINS/component/15683