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?







            Unassigned Unassigned
            p4karl Karl Wirth
            1 Vote for this issue
            2 Start watching this issue