I assume that you had to cancel the child job, what were the reasons that it was still in the queue as mentioned in my previous message.
Also remembered another item that you should check, Make sure that there is a free executor for the child project to run on matching its labels, etc. If is easily reproducible please can you create an issue at https://issues.jenkins-ci.org/ assign to the paramterized-trigger component. listing the Jenkins version, and versions of the plugins you are using including the conditional builder, run-condition, parameterized-trigger. and also attach the config.xml files to the issue for the two jobs. as you are building on the slaves can you also indicate the master/slave config i.e. linux master with 0 executors, slave1 windows with 2 executors that these jobs are tied to. Chris On Monday, 11 February 2013 06:31:49 UTC, Manjunath D G wrote: > > Hi Chris, > Please fidn the Console Output of the failed build. > > > *17:11:16* Started by user x0077055*17:11:16* Building remotely on > dsppc02*17:11:16* Run condition [Always] enabling prebuild for step [Execute > Windows batch command]*17:11:16* Run condition [Always] enabling prebuild > for step [Trigger/call builds on other projects]*17:11:16* Run condition > [Always] enabling perform for step [Execute Windows batch command]*17:11:16* > [Parent] $ cmd /c call > C:\DOCUME~1\TIIAPP~1\LOCALS~1\Temp\hudson4544368964760096002.bat*17:11:16* > *17:11:16* D:\Jenkins_OUT\workspace\Parent>ping localhost -n 10 *17:11:16* > *17:11:16* Pinging dsppc02.apr.dhcp.ti.com [127.0.0.1] with 32 bytes of data: > *17:11:16* > *17:11:16* Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > *17:11:17* Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > *17:11:18* Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > *17:11:19* Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > *17:11:20* Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > *17:11:21* Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > *17:11:22* Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > *17:11:23* Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > *17:11:24* Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > *17:11:25* Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > *17:11:25* > *17:11:25* Ping statistics for 127.0.0.1: > *17:11:25* Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), > *17:11:25* Approximate round trip times in milli-seconds: > *17:11:25* Minimum = 0ms, Maximum = 0ms, Average = 0ms > *17:11:25* *17:11:25* D:\Jenkins_OUT\workspace\Parent>exit 0 *17:11:25* > Run condition [Always] enabling perform for step [Trigger/call builds on > other projects]*17:11:26* Waiting for the completion of *Child* > <http://jenkins-swcoe.india.ti.com/job/Child/>*17:13:06* ERROR: Child > aborted.*17:13:06* Notifying upstream projects of job completion*17:13:06* > Finished: FAILURE > > > Thanks and Regards, > Manju > > On Friday, February 8, 2013 5:06:20 PM UTC+5:30, cjo wrote: > >> >> There is a known issue if the child jobs have "block if upstream is >> running" enabled as they see the triggering job as running, >> which might be the issue that you are seeing. >> >> If this is not the case, can you actually post the reasons that the >> pending jobs are not running (from the tooltip when hovering over the items >> in the Queue), as this will normally indicate the reason for the builds not >> running. >> >> i.e. waiting for an Executor on slave1 or Waiting for Up/Downstream >> project to finish >> >> >> Chris. >> >> >> On Friday, 8 February 2013 07:58:58 UTC, Manjunath D G wrote: >>> >>> Hi All, >>> >>> >>> >>> We have a project (parent) with multiple steps, one of the step being >>> configured as 'trigger/call a build on other projects' (i.e, child job) >>> >>> We have selected the option 'block until the triggered projects finish >>> their builds', so that Parent project will be on hold until the child >>> project gets completed. >>> >>> It works fine if we run the parent project one time. >>> But, if we run another instance of the same Parent project, the child >>> project run (triggered from first run), goes into 'pending forever' state. >>> Similarly, the second Parent project run also goes to 'pending forever' >>> >>> Please let us know if there is any fix/workaround. >>> >>> =========== >>> The projects are configured as: >>> >>> Parent Project:- >>> >>> -Step 1 (Some commands) >>> >>> -Step 2 (Invoke a “Child” project) – parent has to be in wait state >>> until the child completes >>> >>> -Step 3 (Some commands) >>> >>> Child Project:- >>> >>> -Step 1 (Some Commands) >>> ================ >>> >>> Regards, >>> Manju >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
