Pipeline holds executor while waiting for Input

[Vishal Biyani]

Hi,

We have built a pipeline which builds and deploys to Dev environment and after tests deployed to QA. Beyond QA the promotions waits for input for deployment to UAT and Pre-Prod.

Now here is the problem, after artifact has been deployed to QA - promotion to UAT might happen a day or two later. But since pipeline is not finished - it holds an executor.

Is there a way to de-allocate executor and resume after input in a pipeline?

Thanks

-Vishal

[Irfan Sayed]

Hi,

Have you created some custom scripts which waits for some input to process further ? which holds the job from completing successfully and hence executor is not free. executor wont be free for next pipeline unless first one completes.

Are you using rundeck ? for promotion workflow ? you can try that 

HTH

--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4cb2856a-6d92-4157-b99a-c7c991375185%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Baptiste Mathus]

Where did you put the `input` step call?

If you put it *inside* a node {} then it's an expected behaviour. If you put it outside, then it's a bug I would please ask you to file against the tracker.

More precisely:

node {

  ...

  input .. // will hold the node

}

node {

  ...

}

input .. // won't hold it

Cheers

[Vishal Biyani]

Hi Mathus,

Thanks a ton - that's right and worked as expected after moving outside node.

Thanks

-Vishal