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.
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. Thanks, Suresh On Tuesday, March 7, 2017 at 7:50:38 PM UTC+5:30, Travis Camechis wrote: > > 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 this use case in Declarative. >> >> A. >> >> On Mon, Mar 6, 2017 at 2:25 PM R. Tyler Croy <[email protected]> wrote: >> >>> (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 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 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 ? >>> > > > >>> > > >>> > > >>> > > A single stage can use "agent none" >>> > > http://jenkins.io/doc/book/pipeline/syntax/#agent >>> > > >>> > > >>> > > >>> > > - R. Tyler Croy >>> > > >>> > > ------------------------------------------------------ >>> > > Code: <https://github.com/rtyler> >>> > > Chatter: <https://twitter.com/agentdero> >>> > > xmpp: [email protected] <javascript:> >>> > > >>> > > % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F >>> > > ------------------------------------------------------ >>> > > >>> > >>> > -- >>> > 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/c59b475a-35c5-41cd-b7b0-dc2a8b1029c6%40googlegroups.com >>> . >>> > For more options, visit https://groups.google.com/d/optout. >>> >>> >>> - R. Tyler Croy >>> >>> ------------------------------------------------------ >>> Code: <https://github.com/rtyler> >>> Chatter: <https://twitter.com/agentdero> >>> xmpp: [email protected] >>> >>> % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F >>> ------------------------------------------------------ >>> >>> -- >>> 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/20170306222514.j22tdxz6wv552ft4%40blackberry.coupleofllamas.com >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- 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/82ab193e-16cd-42b1-a69f-6a49ab53617b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
