Hi,
Do you think you could create a JIRA for this? This remains a blocker for
us as well and keeps us from running production in a reliable way.
/David
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop re
n context:
http://jenkins-ci.361315.n4.nabble.com/Jenkins-silently-skipping-MultiJob-phase-tp4696480p4715982.html
Sent from the Jenkins users mailing list archive at Nabble.com.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscrib
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 wrote:
> Hi David,
>
> I also experience this issue w
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
--
Y
Hello,
We trigger a parallel batch of roughly 30 parametrized MultiJobs. The
triggering job and each of the phases of the MultiJob can run on one of 2
slave nodes. This is specified via the "Restrict where this job can run"
option.
About 1 in 15 times a phase (mostly the first one) of the Mult
