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.
On Saturday, October 8, 2016, Matthew Grose
wrote:
> Apologies if this isn'
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
jenkin
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.
On Tue, Aug 30, 2016 at 10:32 AM, Andrew Bayer
wrote:
> Hey all -
>
> I've released a first preliminary version (0.1) of a new plu
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 ac
