(replies inline) On Tue, 06 Sep 2016, Mark Waite wrote:
> 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. ci.jenkins.io has had all necessary plugin updates installed. - 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/20160906232155.GI18556%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
