So moving back from flexible DSL to declarative configuration?

2016-09-06 23:41 GMT+03:00 <[email protected]>:

> I assume you are talking about the new plugin created by Andrew Bayer?
>
>
>
> https://jenkins.io/blog/2016/09/06/jenkins-world-speaker-
> blog-pipeline-model-definition/
>
>
>
> https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+
> Model+Definition+Plugin
>
>
>
>
>
>
>
> *From: *Mark Waite <[email protected]>
> *Sent: *September 6, 2016 1:25 PM
> *To: *[email protected]
> *Subject: *Re: Interested in building your plugin on ci.jenkins.io?
>
>
>
>
>
> On Tue, Sep 6, 2016 at 2:08 PM R. Tyler Croy <[email protected]> wrote:
>
> (replies inline)
>
> On Sun, 04 Sep 2016, Mark Waite wrote:
>
> > Is there a plan to update ci.jenkins.io to the latest workflow plugin so
> > that I can switch to uses "{" and  "}" to identify blocks?  I'd like to
> > remove the warning from the jobs I host on my private machines, but I
> don't
> > want to break ci.jenkins.io with a Jenkinsfile that it does not yet
> > understand.
>
>
> I'm not sure I understand what you're referring to. To identify *stage*
> blocks
> I presume?
>
>
>
> Yes, to identify "stage" blocks.  Currently, the git client plugin and the
> git plugin both include a Jenkinsfile on their relevant branches.  Those
> files use the previous syntax:
>
>
>
> node {
>
>   stage 'Checkout'
>
>   checkout scm
>
>   stage 'Build'
>
>   mvn "clean install"
>
> }
>
>
>
> I'd like to switch to the new syntax:
>
>
>
> node {
>
>   stage('Checkout') {
>
>     checkout scm
>
>   |
>
>   stage('Build') {
>
>     mvn "clean install"
>
>   }
>
> }
>
>
>
> If I switch to the new syntax, machines running older versions of the
> pipeline plugins will fail because they don't understand the new syntax.
>
>
>
> Thanks,
>
> Mark Waite
>
>
>
>
> - R. Tyler Croy
>
> ------------------------------------------------------
>      Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> ------------------------------------------------------
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" 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-dev/20160906200817.GF18556%40blackberry.coupleofllamas.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/439-IDYNSVY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CAO49JtGH5V_LDZDd%3DXU9WbLp3b1WrO6SA_
> v7bgJd6scQHqd-0g%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGH5V_LDZDd%3DXU9WbLp3b1WrO6SA_v7bgJd6scQHqd-0g%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/439-IDYNSVY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/57cf29dc.46ec420a.ca6c.09c2%40mx.google.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/57cf29dc.46ec420a.ca6c.09c2%40mx.google.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" 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-dev/CAM9nkw9652gkpS-s_2t0FYBkinm3zb4zABxuXmPFOXr_hjCA2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to