Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-6994

Every build causes an entry in job configuration history

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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)?

        Attachments

          Activity

          Hide
          torbent torbent added a comment -

          Perforce plugin 1.1.9 has fixed this.

          Show
          torbent torbent added a comment - Perforce plugin 1.1.9 has fixed this.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          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

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - 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
          Hide
          torbent torbent added a comment -

          Re-adding component jobconfighistory, as suggested by previous comment(s)

          Show
          torbent torbent added a comment - Re-adding component jobconfighistory, as suggested by previous comment(s)
          Hide
          rpetti Rob Petti added a comment -

          Since no config change is being made (as evidenced by the empty diff) then this seems to be a problem with jobconfighistory.

          Show
          rpetti Rob Petti added a comment - Since no config change is being made (as evidenced by the empty diff) then this seems to be a problem with jobconfighistory.
          Hide
          torbent torbent added a comment -

          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.

          Show
          torbent torbent added a comment - 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.

            People

            • Assignee:
              mfriedenhagen Mirko Friedenhagen
              Reporter:
              torbent torbent
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: