[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
Oleg Nenashev commented on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted I've discovered an issue in the remoting library, which may cause this issue. https://github.com/jenkinsci/remoting/pull/22 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] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
ikedam commented on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted Jenkins = 1.519 (7b2541d) Queue#doCancelItem Queue#cancel(Item) Item#onCancelled FutureImpl#setAsCancelled Jenkins = 1.520 (513a45b) Queue#doCancelItem Queue#cancel(Item) Item#leave Item#onCancelled is removed in 513a45b. I think it should work in following way: Queue#doCancelItem Queue#cancel(Item) Item#cancel Item#leave FutureImpl#setAsCancelled 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] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
ikedam commented on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted This seems introduced in 513a45b. The problem reproduces with that commit, but not with 7b2541d which is the parent of 513a45b. 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
ikedam commented on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted This seems a behavior introduced in Jenkins 1.520. And not fixed even in the latest release (1.553). Jenkins result 1.480.3 don't reproduce 1.509.2 don't reproduce 1.515 don't reproduce 1.517 don't reproduce 1.518 don't reproduce 1.519 don't reproduce 1.520 reproduce 1.532.1 reproduce 1.553 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/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
ikedam commented on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted I found it reproduces even with only one downstream project: Install parameterized-trigger plugin Create a node "slave1" from Manage Jenkins Manage Nodes New Node No need to launch that node. Create a free style project "downstream". Check "Restrict where this project can be run" (this is displayed only when there are slaves) and enter "slave1" to "Label _expression_" Create a free style project "upstream" Add "Trigger/call builds on other projects" "downstream" for "Projects to build" Check Block until the triggered projects finish their builds Click "Build Now" of "upstream". Cancel the build of "downstream" that should be pending. Result: "upstream" should finish, but actually does not finish. And as long I tested, it does not reproduce with Jenkins = 1.509. Jenkins result 1.480.3 don't reproduce 1.509.2 don't reproduce 1.532.1 reproduce I should find the version of Jenkins that starts produce this problem. 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
ikedam commented on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted It reproduced easily also in my environment. Amazing. It would require a fix in Jenkins core as @oleg_nenashev points. How I reproduce: Install parameterized-trigger plugin Create a node "slave1" from Manage Jenkins Manage Nodes New Node No need to launch that node. Create a free style project "downstream1". Check "Restrict where this project can be run" (this is displayed only when there are slaves) and enter "slave1" to "Label _expression_" Create a free style project "downstream2". Create a free style project "upstream" Add "Trigger/call builds on other projects" "downstream1,downstream2" for "Projects to build" Check Block until the triggered projects finish their builds Click "Build Now" of "upstream". Cancel the build of "downstream1" that should be pending. Result: "upstream" should finish, but actually does not finish. Environments: Windows 8 Jenkins 1.532.1 JDK 1.7.0_45 Parameterized Trigger plugin 2.22 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
ikedam assigned JENKINS-21932 to ikedam Job hangs if one of multiple triggered builds was aborted Change By: ikedam (28/Feb/14 11:20 PM) Assignee: huybrechts ikedam 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 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] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
Oleg Nenashev edited a comment on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted I suppose this issue and JENKINS-16679 have the same origin. After the initial analysis of JENKINS-16679 (I've done it several months ago; hope to find notes), I suspect that it may require a fix inside the Jenkins core. As a workaround, it is possible to analyze statuses of future tasks instead of sequential "wait" calls against the submitted projects list. 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
ikedam updated JENKINS-21932 Job hangs if one of multiple triggered builds was aborted Sounds a issue of parameterized-trigger plugin. Can you always reproduce that behavior? Please report an example project configuration to reproduce the problem. Change By: ikedam (26/Feb/14 11:38 PM) Assignee: DominikBartholdi huybrechts Component/s: nodelabelparameter 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.
