if you are using all the executors then you are using the "input" step 
inside a node block.
Use it outside of a node block and it won't consume any executors (and IIRC 
as of recently it won't consume any threads either!)

If you need access to your files (which may be true if you are keeping the 
node active) use the stash/unstash command (1.10) to store and retrieve 
them.

SO that will fix your executor issue - the next issue is leaving 1000+ 
builds waiting for user input....
It really depends on your flow - do you want to wait 14 days for that one 
build in dev to to be authorised to production?

If not - then wrap the input with a timeout - which will then abort the 
build if no one wants to promote it.
Do you have multiple dev environments?  if not then you can also kill the 
waiting for ok to promote to production when a later build is promoted to 
dev.



On Thursday, October 8, 2015 at 4:08:25 PM UTC+2, Martin d'Anjou wrote:
>
> I think I am using the Workflow manual input step incorrectly. I must 
> misunderstand the problem it solves.
>
> My pipeline has several steps:
> 1) compiler phase 1 and test (1 hour)
> 3) manually decide whether to stop or continue to step 4
> 4) compiler phase 2 and more tests (2 to 4 hours)
> 5) manually decide whether to stop or continue to step 6
> 6) deploy to dev
> 7) manually decide whether to stop or continue to step 8
> 8) deploy to production
>
> Only a few, out of thousands, make it to production. When I use the 
> Workflow plugin with the manual input step, it leaves builds with balls 
> blinking waiting for user input. Also, pausing eventually blocks all 
> execution slots. With thousands of builds, this can't be right.
>
> This cannot be how the manual input is intended to work. How do people do 
> manual build steps that depend on upstream jobs?
>
> Thanks,
> Martin
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/13693a47-605b-4fd4-8eb9-7647010dfc53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to