Both of them are good but they have different approaches... Although, IMO, Pipeline is still an incubating feature atm. I wouldn't say Pipelines are better or worst or even obsolete or modern. If you go for configuration as code, by definition, code should be testable, and I could go further by saying testable locally and automatically, and unfortunately I haven't not seen that feature yet with the Pipelines.
Cheers On Monday, 7 November 2016 20:53:35 UTC, Michael Lasevich wrote: > > Ahh, "Job DSL", I remember that. It was a good thing when it was the only > game in town, but (in my opinion) Pipelines pretty much made it obsolete. > Of course it is a matter of opinion, but if you are finding Jobs DSL too > complicated, Pipelines may be just right for you - it removes a lot of the > complexity, and makes your entire build process far simpler - you no longer > need a rabbit-warren of jobs, and with MultiBranch Pipelines + Global Libs > + something like Slack notifications, your devs may not even need to login > to Jenkins server - just commit code and see notification that the job was > created(if needed) and build was complete :-) Join the modern age :-) > > -M > > On Monday, November 7, 2016 at 11:55:20 AM UTC-8, Victor Martinez wrote: >> >> Give a try job-dsl-plugin >> - https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin >> >> Supports 1000+ jenkins plugins, local testing, gradle integration, same >> Jenkins job paradigm, DRY concept and a bunch of other benefits besides of >> converting jobs in code and therefore scm oriented. >> >> Cheers >> >> -- 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/82387c59-9217-42fb-bbe3-d8ce9740b114%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
