New Pipeline plugin: Pipeline Model Definition

166 views
Skip to first unread message

Andrew Bayer

unread,
Aug 30, 2016, 1:33:30 PM8/30/16
to jenkin...@googlegroups.com, jenkins...@googlegroups.com
Hey all -

I've released a first preliminary version (0.1) of a new plugin, Pipeline: Model Definition. It's intended to provide a more config-like/declarative way to define Pipelines, with features like better syntactic/semantic error messages, an easy way to specify notifications or post-build actions to run regardless of build status, and more. 

It's still very early on - this is basically an MVP, so I wouldn't recommend using it in production yet, but I intend to keep backwards compatibility working as we go forward. You can find the repo at https://github.com/jenkinsci/pipeline-model-definition-plugin, with early docs at https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki and a spec for the model syntax at https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/SYNTAX.md - I'd love feedback! Thanks!

A.

Andrew Bayer

unread,
Aug 31, 2016, 2:45:18 PM8/31/16
to jenkin...@googlegroups.com, jenkins...@googlegroups.com
Oh, and I'll be presenting on this at Jenkins World on Thursday the 15th in the afternoon, with a demo during lunch time, and will be around to chat all week. =)

A.

Matthew Grose

unread,
Oct 7, 2016, 7:00:30 PM10/7/16
to Jenkins Users, jenkin...@googlegroups.com
Apologies if this isn't the right forum.. after installing BlueOcean beta this plugin came in as dependency. It appears it tries to now run all of our existing jenkinsfile pipelines under the model definition. Was able to remove blue ocean and the model definition plugin and the existing jenkinsfile's starting working again.  It appears the installation of the plugin force adopts all jenkinsfile's to use configuration over code, is this expected? is there a way to differentiate between the two options for certain jenkinsfiles?

Andrew Bayer

unread,
Oct 8, 2016, 3:38:17 AM10/8/16
to jenkins...@googlegroups.com, jenkin...@googlegroups.com
It's *definitely* not supposed to do that! The declarative model should only kick in if you're using the "pipeline { ... }" step. Can you open a ticket on issues.jenkins-ci.org with the errors you're getting? Thanks!

A.
--
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-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b652a1bf-e601-4bbc-b7bd-832aea508af1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages