[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
Sergey Irisov updated JENKINS-21932 Job hangs if one of multiple triggered builds was aborted Change By: Sergey Irisov (27/Feb/14 8:52 AM) Attachment: slave2_config.xml Attachment: launcher_multiple_job_config.xml Attachment: slave1_config.xml 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/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
Sergey Irisov commented on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted I can reproduce now only first case. Parent job: Launcher_trigger_multiple_job. It triggers 2 job: Slave_job and Slave_job2. Slave_job was aborted while it stays in queue. And Slave_job2 successfully finished. Launcher job hung waiting for Slave_job. 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/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
Sergey Irisov edited a comment on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted I can reproduce now only first case. Parent job: Launcher_trigger_multiple_job. It triggers 2 job: Slave_job and Slave_job2. Slave_job was aborted while it stays in queue. And Slave_job2 successfully finished. Launcher job hung waiting for Slave_job. Jobs' configs are in attachment. 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/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
Sergey Irisov created JENKINS-21932 Job hangs if one of multiple triggered builds was aborted Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter, parameterized-trigger Created: 24/Feb/14 10:18 AM Description: I have two cases with job hanging: 1) Parent job triggers multiple different jobs and waits for their completion. I abort some triggered job while it stays in queue. After that parent job never finished, waiting for completion. 2) Parent job triggers multiple instances (via label factory) of one job on different slaves and waits for completion. I abort one of job while it executes on slave. Parent job hangs forever saying "Waiting for completion". I believe it worked correctly (in both cases parent job has failed) in some previous version. I've recently updated Jenkins from 1.48 to 1.532 As well as Parametrized Trigger Plugin from 2.16 to 2.22 And NodeLabel Parameter Plugin from 1.2.1 to 1.4 Project: Jenkins Priority: Major Reporter: Sergey Irisov 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/groups/opt_out.
