So I was not running in a node block I will do more testing thank you.
Here is a sample of my code:
*#!groovy*
*import hudson.model.**
*stage('many_jobs') {*
*parallel (get_many_jobs(6000))*
*}*
*def get_many_jobs(num_builds) {*
*// The map we'll store the parallel steps in before
So I have not run in an ode block I will do more testing thank you.
Here is a sample of my code:
*#!groovy*
*import hudson.model.**
*stage('many_jobs') {*
*parallel (get_many_jobs(6000))*
*}*
*def get_many_jobs(num_builds) {*
*// The map we'll store the parallel steps in before
Hey there -
I think it might be worth posting the pipeline of your orchestration job
that runs the 12000 builds for anyone to comment in more detail.
>From what I understand, if your pipeline is not orchestrating each build in
a node section it will use something called a 'flyweight executor'
So not sure if this is a Jenkins limitation or pipeline.
The jobs never exceeded available resources.
The garbage collection was stable.
So why did it lock-up?
It did say I used
- 2950 million active threads
- 350 threads
--
You received this message because you are subscribed to the
I need to retry it may be that the jobs never all started
Branch: job_0 - (1ms in block)
Branch: job_9830 - (3min 16sec in block)
Branch: job_9831 - (No timing in block)
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this
So 3 hr 30 min later the pipeline is locked up
--
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.
To view this
