The declarative option is nice but you will lose the ability to extract out
reusable code via the shared library. For example, you can't do this yet:
MyCompanyStandardPipeline {
... // which will plugin standard sections...
}
On Thursday, March 16, 2017 at 8:55:48 PM UTC-7, Nick Le Mouton wrote:
>
> Hi,
>
> I'm just getting my head around pipeline as code and have converted my
> previous Jenkins job/ant build targets to a Jenkinsfile. As I was looking
> for documentation on the Jenkins site, I'm seeing mentions of declarative
> pipelines and it differs from what I've written.
>
> Which method should I be looking to use (especially with blue ocean)?
> Declarative or scripted? Why should I be using one over the other?
>
> Can I also get some feedback on my Jenkinsfile (
> https://gist.github.com/NoodlesNZ/bf9b50cab82093097796d354e37083f0)? It's
> hard to find examples beyond "hello world"/simple pipelines.
>
> Thanks
>
--
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/fdd17e1a-35fa-41b2-bd16-e5c136a456f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
