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

Suppress tracking changes

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: perforce-plugin
    • Labels:
      None
    • Environment:
      Platform: Other, OS: Windows XP
    • Similar Issues:

      Description

      When perforce synchronizes with its workspace it tries find the changelist
      descriptions. We see this in the log file as follows:
      "[workspace] $ p4 describe -s 12865"

      Usually we are not interested in these change descriptions at all. Can we
      suppress retrieving change list descriptions. It does take a lot of time to
      retrieve them all !

        Attachments

          Activity

          Hide
          kohsuke Kohsuke Kawaguchi added a comment -

          Un-assigning this from digerata per request by him.

          Show
          kohsuke Kohsuke Kawaguchi added a comment - Un-assigning this from digerata per request by him.
          Hide
          numericalexample_com numericalexample_com added a comment -

          A workaround is entering a very high change list number in the field "First
          change list to track" and clicking the flag "Force sync". In that case the
          plugin only lists the changes after the given change number and still does a
          complete sync.

          What I did not understand before is that the field "First change list to track"
          only deals with the change list in the hudson project. It does not have anything
          to do with the synchronization of the project sources with the perforce server.

          This issue can be closed now.

          Show
          numericalexample_com numericalexample_com added a comment - A workaround is entering a very high change list number in the field "First change list to track" and clicking the flag "Force sync". In that case the plugin only lists the changes after the given change number and still does a complete sync. What I did not understand before is that the field "First change list to track" only deals with the change list in the hudson project. It does not have anything to do with the synchronization of the project sources with the perforce server. This issue can be closed now.
          Hide
          jsynge jsynge added a comment -

          I've changed the computation of the first change list to track so that for new project/job it does not start from 0, but rather assumes that no changes should be
          reported (i.e. not until there is a change introduced between two builds of the
          job). This should hopefully address the original concern (too many changes).

          It may still be of interest to have the feature: don't determine/save the changes
          for builds of this project.

          Show
          jsynge jsynge added a comment - I've changed the computation of the first change list to track so that for new project/job it does not start from 0, but rather assumes that no changes should be reported (i.e. not until there is a change introduced between two builds of the job). This should hopefully address the original concern (too many changes). It may still be of interest to have the feature: don't determine/save the changes for builds of this project.

            People

            • Assignee:
              Unassigned
              Reporter:
              numericalexample_com numericalexample_com
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: