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

Can we cache or get rid of the initial 'p4 changes -m1 //WS/...@CL'

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • P4-Plugin 1.12.1

      At the start of each job P4-Plugin runs 2 changes -m1 commands. 

      p4 changes -m1 -ssubmitted //WS/...@CL
      p4 changes -m1 -ssubmitted //WS/...@CL,CL 

      The second command can be influenced by the setting 'Head Change Query Limit' however for small incremental builds on large P4D servers the first command can take the same time or longer than the actual sync. For example:

      11:31:16 p4 changes -m1 -ssubmitted //WS1/...@22003775
      11:31:32 Change 22003775 on 2022/04/01 by user@ws 'CL description' 

      On busy systems there can be more than 5000 of these run per hour putting a large load on dedicated well spec'd build P4D edge replicas.

      Is there any way (such as caching) that we can avoid the expensive 'p4 changes -m1' query?

       

       

       

       

       

       

          [JENKINS-68324] Can we cache or get rid of the initial 'p4 changes -m1 //WS/...@CL'

          Velusamy Krishnan added a comment - - edited

          Also this "m1 -ssubmitted" is running for all the branches in a repository even when a specific branch build triggered on "Multi Branch pipeline" configurations. This behavior adds a lot of time of the builds if repository contains many branches.

          Could someone please check  this and provide us some solutions?

           

          Thanks,

          Velu.

          Velusamy Krishnan added a comment - - edited Also this "m1 -ssubmitted" is running for all the branches in a repository even when a specific branch build triggered on "Multi Branch pipeline" configurations. This behavior adds a lot of time of the builds if repository contains many branches. Could someone please check  this and provide us some solutions?   Thanks, Velu.

          Karl Wirth added a comment -

          velkrish - Please see JENKINS-64946 for the changes -m1 topic on every branch.

          Karl Wirth added a comment - velkrish - Please see JENKINS-64946 for the changes -m1 topic on every branch.

          Dhaval added a comment - - edited

          Hi velkrish ,
          P4changes should not take longer that sync ideally. 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 

          Dhaval added a comment - - edited Hi velkrish , P4changes should not take longer that sync ideally. 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  

            Unassigned Unassigned
            p4karl Karl Wirth
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: