[JIRA] (JENKINS-34037) P4 polling always triggers if matrix axis is built on a different slave

[timothy.fredrick...@seagate.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Fredrickson closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34037  
 
 
  P4 polling always triggers if matrix axis is built on a different slave   
 

  
 
 
 
 

 
Change By: 
 Tim Fredrickson  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-34037) P4 polling always triggers if matrix axis is built on a different slave

[timothy.fredrick...@seagate.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Fredrickson resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34037  
 
 
  P4 polling always triggers if matrix axis is built on a different slave   
 

  
 
 
 
 

 
Change By: 
 Tim Fredrickson  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-34037) P4 polling always triggers if matrix axis is built on a different slave

[jbr...@perforce.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown commented on  JENKINS-34037  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: P4 polling always triggers if matrix axis is built on a different slave   
 

  
 
 
 
 

 
 Actually, I see polling always triggering a build for a matrix job with a build axis: After the first poll we see these 5 clients (job name is matrix) Client jenkins-jbrown-centos7-matrix-label-jbrown-centos7 2016/09/08 root /jenkins-slave/workspace/matrix/label/jbrown-centos7 'Change:592 ' Client jenkins-jbrown-p4-u15.das.perforce.com-matrix-label-jbrown-p4-u15.das.perforce.com 2016/09/08 root /jenkins-slave/workspace/matrix/label/jbrown-p4-u15.das.perf orce.com 'Change:592 ' Client jenkins-master-matrix 2016/09/08 root /var/lib/jenkins/jobs/matrix/workspace '' Client jenkins-master-matrix-label-jbrown-centos7 2016/09/08 root null '' Client jenkins-master-matrix-label-jbrown-p4-u15.das.perforce.com 2016/09/08 root null '' I added "Description: Change 592" to the 3 jenkins-master-matrix* clients, it will then build.  After the next build: Client jenkins-jbrown-centos7-matrix-label-jbrown-centos7 2016/09/08 root /jenkins-slave/workspace/matrix/label/jbrown-centos7 'Change:593 ' Client jenkins-jbrown-p4-u15.das.perforce.com-matrix-label-jbrown-p4-u15.das.perforce.com 2016/09/08 root /jenkins-slave/workspace/matrix/label/jbrown-p4-u15.das.perf orce.com 'Change:593 ' Client jenkins-master-matrix 2016/09/08 root /var/lib/jenkins/jobs/matrix/workspace 'Change: 592 ' Client jenkins-master-matrix-label-jbrown-centos7 2016/09/08 root null 'Change: 592 ' Client jenkins-master-matrix-label-jbrown-p4-u15.das.perforce.com 2016/09/08 root null 'Change: 592 ' The jenkins-master-matrix* clients are used for polling - that description didn't change so it builds again. My setup: Create a stream depot with depth=2 put some files into the stream – e.g., //stream2/simple-ant/main Create two additional slave nodes (all master/slaves all unix) Create matrix (Mulit-configuration) project (I called in matrix). Check disable this project for now. 
 
Take defaults for SCM (workspace name of jenkins-$ {NODE_NAME} -$ {JOB_NAME} , Auto cleanup and sync, uncheck quiet) 
 Build triger: Poll SCM (I used H/5 * * * *) Add axis: slaves. Check your two nodes (master not checked)  I let polling trigger the first build.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment