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

The ability to prevent P4-Plugin from running the p4 changes -m20 //depot/path/...@<last run>,<this run> in each run.

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Critical Critical
    • p4-plugin
    • None
    • P4D/LINUX26X86_64/2019.2/1918134.
      Jenkins Plug-in: 1.12.2

      The ability to prevent P4-Plugin from running the p4 changes -m20 //depot/path/...@<last run>,<this run> in each run.
      P4-Plugin runs the p4 changes -m20 command when the current build syncs to a label/change that is different from the one the last build synced.
      The p4 changes command can be very expensive especially when a large label/change is involved. The comparison done using the command is not necessary when each build is independent of the previous one. The customer hoped that using the "Force clean and sync" option in the P4-Plugin would make each run ignore previous state information so that the P4-Plugin won't run the p4 changes -m20 command, but that was not the case.
      The customer would like to have the ability to prevent P4-Plugin from running the p4 changes -m20 //depot/path/...@<last run>,<this run>.

          [JENKINS-68365] The ability to prevent P4-Plugin from running the p4 changes -m20 //depot/path/...@<last run>,<this run> in each run.

          Andrew Ray added a comment -

          Is this a duplicate of JENKINS-68324?

          Andrew Ray added a comment - Is this a duplicate of JENKINS-68324 ?

          Dhaval added a comment - - edited

          Hi isc_aray  ,
          P4changes should not take so much time. We couldnot recreate the issue, requesting you to share config.xml, build.xml and log.xml for further investigation.
          Files can either be shared here or to support@perforce.com mentioning this jenkins ticket.

          Also please check how much time running a p4 changes command takes from command line directly and let us know. Does it take same amount of time as it takes from Jenkins?

          Thanks .

          CC: p4karl skumar7322 cchoi 

          Dhaval added a comment - - edited Hi isc_aray   , P4changes should not take so much time. We couldnot recreate the issue, requesting you to share config.xml, build.xml and log.xml for further investigation. Files can either be shared here or to  support@perforce.com  mentioning this jenkins ticket. Also please check how much time running a p4 changes command takes from command line directly and let us know. Does it take same amount of time as it takes from Jenkins? Thanks  . CC:  p4karl   skumar7322 cchoi  

            Unassigned Unassigned
            cchoi Christopher Choi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: