[JIRA] [core] (JENKINS-29217) Parent job thinks it called child job, but child job never starts.

[jesseforr...@gmail.com (JIRA)]

Title: Message Title

Jesse Forrest updated an issue   Jenkins / JENKINS-29217 Parent job thinks it called child job, but child job never starts. Change By: Jesse Forrest I should start off by saying that I tried to find information on the web related to this issue, but was not able to.  So I apologize if this is a duplicate bug report. I currently have a Jenkins job, "Rollup_Stage", that uses the parameterized trigger plugin to call multiple child jobs ("Deploy_iOS_IPA" and "Deploy_Stage").  Here is the screenshot: !Screen Shot 2015-07-03 at 8.30.43 AM.png|thumbnail! This configuration worked consistently for a long time, but in the past month we have noticed a strange behavior. This issue is happening more and more frequently over time. The issue is that the parent job thinks it called the child job, but the child job never gets triggered. For example, this is the what we're seeing on the parent job "Rollup_Stage": !Screen Shot 2015-07-03 at 8.29.29 AM.png|thumbnail! Notice that it thinks it started "Deploy_Stage": !Screen Shot 2015-07-03 at 8.29.35 AM.png|thumbnail!  However, if you look at this screenshot  which shows the build history for "Deploy_Stage"  you will notice that "Deploy_Stage" never started: !Screen Shot 2015-07-03 at 8.29.45 AM.png|thumbnail! What's strange is that the other job "Deploy_iOS_IPA" is consistently running as expected, but from some reason the "Deploy_Stage" job is not starting.   Any advice on how to diagnose the issue would be appreciated. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.