[JIRA] [build-flow] (JENKINS-22502) Matrix parent occupies an executor and blocks child jobs from execution if appropriate slave becomes online after matrix job was already in the queue

2014-06-26 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 resolved  JENKINS-22502 as Cannot Reproduce


Matrix parent occupies an executor and blocks child jobs from execution if appropriate slave becomes online after matrix job was already in the queue
















Cannot reproduce the problem on 1.567, the matrix parent correctly uses a one-off executor on the swarm node.

No response to follow-up questions by reporter in a few weeks, so resolving as Cannot Reproduce.





Change By:


Daniel Beck
(26/Jun/14 11:55 AM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [build-flow] (JENKINS-22502) Matrix parent occupies an executor and blocks child jobs from execution if appropriate slave becomes online after matrix job was already in the queue

2014-06-09 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-22502


Matrix parent occupies an executor and blocks child jobs from execution if appropriate slave becomes online after matrix job was already in the queue















Matrix parent should use a one-off executor and not block regular tasks. Did you disable flyweight support? What's the output of 
Jenkins.FLYWEIGHT_SUPPORT
 in Script Console? Could you provide a screenshot of the queue and executors list when you're "stuck"?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [build-flow] (JENKINS-22502) Matrix parent occupies an executor and blocks child jobs from execution if appropriate slave becomes online after matrix job was already in the queue

2014-04-04 Thread li...@mail.ru (JIRA)














































Vadim Lipatov
 created  JENKINS-22502


Matrix parent occupies an executor and blocks child jobs from execution if appropriate slave becomes online after matrix job was already in the queue















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


build-flow, core



Created:


04/Apr/14 12:56 PM



Description:


There is a matrix job with 1 axis and 3 child jobs.
A label of slaves for execution is assigned via parameter using LabelNode plugin.
Initially there is no available executors in the system.


To reproduce:

	run the matrix job with the label parameter "exp_label1". Job is set to the queue;
	run the swarm slave and assign it the same label that provided in the parameter for the job: "exp_label1".
	the swarm slave appears in the list of executors and matrix parent occupies it. After that 3 child jobs are set to the queue forever.



I tried to use MatrixTieParent plugin but it looks it does not work correctly with NodeLabel plugin.




Environment:


Windows 7, 64bit, jdk 1.7.0_21




Project:


Jenkins



Priority:


Major



Reporter:


Vadim Lipatov

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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.