-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: jobconfighistory-plugin
-
Labels:None
-
Similar Issues:
I've noticed that my job configuration history is "spammed" with changes that the system, not a user, makes.
The changes in mind concern "changelogFilename" (if I remember correctly) and seems like it should be a property of a build, not a job, and thus not appear in the job configuration history.
The job configuration history pages take a very long time to load because of all these changes, and it's difficult to spot the real changes, where a user has changed something in the configuration.
Is this an issue with the plugin (for reporting it as a change) or in core (for having this info on the job)?
Are you using the perforce plugin? I just emailed the dev mailing list about this problem, and I think it is PerforceSCM class fault.
It is here: http://hudson.361315.n4.nabble.com/Perforce-SCM-is-polluting-the-config-xml-td2329663.html#a2329663