[JIRA] (JENKINS-58034) Pipeline job is being shown on two executors (master and node) while inside p4step

17 views
Skip to first unread message

delikat.mateusz@gmail.com (JIRA)

unread,
Jun 16, 2019, 5:34:03 PM6/16/19
to jenkinsc...@googlegroups.com
Mateusz Delikat created an issue
 
Jenkins / Bug JENKINS-58034
Pipeline job is being shown on two executors (master and node) while inside p4step
Issue Type: Bug Bug
Assignee: Unassigned
Components: p4-plugin
Created: 2019-06-16 21:33
Environment: p4 plugin 1.10
Jenkins 2.176.1
Priority: Major Major
Reporter: Mateusz Delikat

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
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

kwirth@perforce.com (JIRA)

unread,
Jun 17, 2019, 4:38:03 AM6/17/19
to jenkinsc...@googlegroups.com
Karl Wirth commented on Bug JENKINS-58034
 
Re: Pipeline job is being shown on two executors (master and node) while inside p4step

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

 

kwirth@perforce.com (JIRA)

unread,
Jun 20, 2019, 7:37:02 AM6/20/19
to jenkinsc...@googlegroups.com

Hi Mateusz Delikat,

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

Regards,

Karl

kwirth@perforce.com (JIRA)

unread,
Jun 20, 2019, 8:19:03 AM6/20/19
to jenkinsc...@googlegroups.com
Karl Wirth assigned an issue to Karl Wirth
 
Change By: Karl Wirth
Assignee: Karl Wirth

delikat.mateusz@gmail.com (JIRA)

unread,
Jun 20, 2019, 5:19:02 PM6/20/19
to jenkinsc...@googlegroups.com
Mateusz Delikat commented on Bug JENKINS-58034
 
Re: Pipeline job is being shown on two executors (master and node) while inside p4step

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

kwirth@perforce.com (JIRA)

unread,
Jun 21, 2019, 4:14:02 AM6/21/19
to jenkinsc...@googlegroups.com
Karl Wirth updated an issue
 
Change By: Karl Wirth
Attachment: image-2019-06-21-09-13-30-063.png

kwirth@perforce.com (JIRA)

unread,
Jul 1, 2019, 11:34:03 AM7/1/19
to jenkinsc...@googlegroups.com
Karl Wirth updated an issue
Change By: Karl Wirth
Labels: P4_SUPPORT

kwirth@perforce.com (JIRA)

unread,
Jul 11, 2019, 10:58:02 AM7/11/19
to jenkinsc...@googlegroups.com

kwirth@perforce.com (JIRA)

unread,
Nov 25, 2019, 12:49:03 PM11/25/19
to jenkinsc...@googlegroups.com

I hit a brick wall with this one. Cannot see any activity  on the Perforce side and unable to find a generic tracing that tells me what a node (slave or master) is up to.
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages