-
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)?
Yes, I am indeed using the Perforce plugin. I'll switch the issue over to the plugin, if I can.
Is an issue in the Perforce plugin.
Code changed in hudson
User: : rpetti
Path:
trunk/hudson/plugins/perforce/src/main/java/hudson/plugins/perforce/PerforceSCM.java
http://jenkins-ci.org/commit/33967
Log:
[FIXED JENKINS-6994] setting changeLogFilename to transient so it doesn't pollute the config.xml
Not a problem of jobconfighistory.
I've installed the newest perforce plugin + core (1.374) and there are no longer "changelogFilename" changes for every build. But there's still a configuration change! When I take a diff, it's empty (does not display any changes). IMHO, such a "change" should not be logged.
Since no config change is being made (as evidenced by the empty diff) then this seems to be a problem with jobconfighistory.
Re-adding component jobconfighistory, as suggested by previous comment(s)
Code changed in hudson
User: : rpetti
Path:
trunk/hudson/plugins/perforce/src/main/java/hudson/plugins/perforce/PerforceSCM.java
http://jenkins-ci.org/commit/34556
Log:
JENKINS-6994 work-around to prevent perforce plugin from logging a 'change' every build
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