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/d4e00c68-787e-451e-a1f7-dcf8b627d431%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
