No, the issue persists and I have not found a work-around. Initially, I thought it may be related to out-of-memory issues in Jenkins but it turns out that this is not the case.
Regards, /David On Wed, May 28, 2014 at 9:34 AM, Scott Tenorman <[email protected]>wrote: > Hi David, > > I also experience this issue with 18 child jobs. > I tried to split parent job into 3 but it does'nt solve the problem. I > also tried to use build-flow-plugin but it doesn't fill my requirements. > > Has someone also seen the issue ? Or David, did you find a workaround ? > > Regards > > Marc > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/vva7-dLYQL4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
