Re: Interactive input with new DSL

The general recommendation is to look for it in the tracker, then file it as thoroughly as possible if not. Thanks Le 17 mars 2017 2:40 PM, "Peter Marcoen" a écrit : > I experience the same effect. > > I have a top-level agent definition for the agent I want to use by

Re: Interactive input with new DSL

I experience the same effect. I have a top-level agent definition for the agent I want to use by default. In some underlying step I want to use a very specific agent, this override works great. However, if I use "agent none" in an underlying step to accept input, the "default" node is still

Re: Interactive input with new DSL

Tried with 'agent none' with stage having input step, it is not occupying the executor and the pipeline status showing Pause but build status is still Running. Is there a possibility stopping the build there and on demand basis according to user wish he/she may select the pipeline version

Re: Interactive input with new DSL

On Thu, 9 Mar 2017, at 05:13, suresh kumar wrote: > I see another thing which is missing in pipelines "post build steps". How > Jenkins community is addressing this, Is there any such document or notes > which explains this? This will help me. There is documentation for Declarative Pipeline:

Re: Interactive input with new DSL

If we keep "agent none", pipeline input step wont occupy the any executor until the user approves or rejects. Is this current behavior like this? I will give a try some time today, this feature really required for my CD solution. We planning to move from freestyle projects to pipeline scripts.

Re: Interactive input with new DSL

hmm, if thats the case then this seems like a major flaw I would think. Also a necessary one for a lot of CD pipelines. On Monday, March 6, 2017 at 10:03:29 PM UTC-5, Andrew Bayer wrote: > > Actually, "agent none" on a stage does nothing. I'm still trying to find > an effective way to solve

Re: Interactive input with new DSL

Actually, "agent none" on a stage does nothing. I'm still trying to find an effective way to solve this use case in Declarative. A. On Mon, Mar 6, 2017 at 2:25 PM R. Tyler Croy wrote: > (replies inline) > > On Mon, 06 Mar 2017, Travis Camechis wrote: > > > So if you define

Re: Interactive input with new DSL

(replies inline) On Mon, 06 Mar 2017, Travis Camechis wrote: > So if you define an agent of none within a stage it will override the > higher level pipeline stage ? Correct, the previously linked documentation has an example of a stage-level "agent" directive. > On Monday, March 6, 2017 at

Re: Interactive input with new DSL

So if you define an agent of none within a stage it will override the higher level pipeline stage ? On Monday, March 6, 2017 at 2:39:42 PM UTC-5, R Tyler Croy wrote: > > (replies inline) > > On Mon, 06 Mar 2017, Travis Camechis wrote: > > > With scripted DSL your not supposed to ask for input

Interactive input with new DSL

With scripted DSL your not supposed to ask for input inside a node so you don't tie up an executor while waiting for user input. How is this same thing accomplished in the new DSL ? It seems like everything runs inside a node with the new DSL ? Thanks Travis -- You received this message