I do like this solution and it seems really flexible but unfortunately it has one big problem for us. The build is not technically *done* until this input step is answered. Sometimes we will want to release over a week later. We release at any time really. If we timeout then we can't answer the input step, but if we don't timeout then the build does not finish. It would be lovely if we could specify an input step between two different jobs, or split it in some way so we can have builds completing and later decide to continue some builds to the deploy stage.
On Monday, August 21, 2017 at 10:54:46 AM UTC+1, Ludovic SMADJA wrote: > > Actually we are using a input step without a timeout fixed to one day (in > order to deploy the version which was deployed during the last night on > pre-prodcution server). > > If you catch the timeout exception without any error, This tricks do the > job. > > -- > > Ludovic SMADJA > R&D engineer - build process and development JALIOS SA > http://www.jalios.com > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/93818a64-f2c0-4c76-9ba7-ffe71ce08c63%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
