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

Pipeline job is being shown on two executors (master and node) while inside p4step

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: p4-plugin
    • Labels:
    • Environment:
      p4 plugin 1.10
      Jenkins 2.176.1
    • Similar Issues:

      Description

      Hello,

      After updating P4 Plugin to 1.10 and Jenkins to 2.176.1 we've noticed that when jobs are sync'ing with P4SYNC step - they're running on master executor and destinated node executor at the same time. Job dissapears from master executor as soon as P4SYNC finishes.

      P4SYNC step is being called within node("${label}"){} block, so it should be running exclusively on the slave with selected label (where the label is not "master"). 

      This leads to some confusion about where the job is actually running and why exactly is it utilizing master.

       

      Best regards,

      Mateusz

        Attachments

          Activity

          Hide
          p4karl Karl Wirth added a comment -

          Hi Mateusz Delikat,

          Thanks for reporting this. Can you provide more information:

          (1) How can you see that it's running on both master and slave at the same time?

          (2) What versions did you upgrade from?

          (3) If possible please upload your Jenkinsfile.

          (4) Is this a pipeline or multi-branch pipeline job?

           

          Thanks in advance,

          Karl

           

          Show
          p4karl Karl Wirth added a comment - Hi Mateusz Delikat , Thanks for reporting this. Can you provide more information: (1) How can you see that it's running on both master and slave at the same time? (2) What versions did you upgrade from? (3) If possible please upload your Jenkinsfile. (4) Is this a pipeline or multi-branch pipeline job?   Thanks in advance, Karl  
          Hide
          p4karl Karl Wirth added a comment -

          Hi Mateusz Delikat,

          I just wanted to check in to see if you had seen my previous message.

          Regards,

          Karl

          Show
          p4karl Karl Wirth added a comment - Hi Mateusz Delikat , I just wanted to check in to see if you had seen my previous message. Regards, Karl
          Hide
          mdelikat Mateusz Delikat added a comment -

          Hey Karl Wirth,

          Sorry for a delay in my response. 

          1. I can see my job in Build Executor Status panel both under master and a node that it's supposed to be running on when it's during p4sync step. When the p4sync finishes - job dissapears from under master executors and stays on the correct worker until it finishes.
          2. Jenkins ver. 2.150.2, p4 plugin 1.9.4.
          3. Sadly it's not possible for me to upload the exact jenkinsfile, but I've managed to replicate this issue with using this script (omitted syncOnly options - they're were left default):
          node("node-name"){
             ws("workspace-path"){
                p4sync (
                   charset: 'none',
                   credential: 'xxx', 
                   format: 'workspace-name',
                   populate: syncOnly(...),
                   source: streamSource('//depot/stream')
                )
             }
          }
          1. It's a pipeline - Scripted Pipeline to be exact.

           

          Best,

          Mateusz

          Show
          mdelikat Mateusz Delikat added a comment - Hey Karl Wirth , Sorry for a delay in my response.  I can see my job in Build Executor Status panel both under master and a node that it's supposed to be running on when it's during p4sync step. When the p4sync finishes - job dissapears from under master executors and stays on the correct worker until it finishes. Jenkins ver. 2.150.2, p4 plugin 1.9.4. Sadly it's not possible for me to upload the exact jenkinsfile, but I've managed to replicate this issue with using this script (omitted syncOnly options - they're were left default): node( "node-name" ){ ws( "workspace-path" ){ p4sync ( charset: 'none' , credential: 'xxx' , format: 'workspace-name' , populate: syncOnly(...), source: streamSource( ' //depot/stream' ) ) } } It's a pipeline - Scripted Pipeline to be exact.   Best, Mateusz
          Hide
          p4karl Karl Wirth added a comment -

          Note - Working directly with Mateusz on this case.

          Show
          p4karl Karl Wirth added a comment - Note - Working directly with Mateusz on this case.

            People

            • Assignee:
              p4karl Karl Wirth
              Reporter:
              mdelikat Mateusz Delikat
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: