Thanks for the great feedback, everyone! These are all good arguments and I've been convinced of the benefits of using distinct jobs for each project. Thankfully, the Job DSL plugin makes this trivial.
Cheers! On Friday, August 12, 2016 at 4:53:15 PM UTC-4, Rich Schumacher wrote: > > Hey folks, > > > I'm using the Job DSL plugin to create CI/CD pipelines for a bunch of > projects. The projects themselves are very similar and therefore the jobs > for build and release will be nearly identical, differing only in stuff > like Git repo to clone, email address for notifications, etc. I've been > going back and forth about using distinct jobs for each project or to use a > parameterized job for each step of the pipeline. The former leads to a > proliferation of jobs that are nearly identical. The latter leads to jobs > that might have 3-6 parameters and means it's difficult to use directly > since you'll need to define all the parameters. The nice thing is that the > Job DSL plugin makes either case pretty easy to support. > > > So my question is really about best practices and preferences: many > distinct jobs vs a handful of parameterized jobs? Are there any non-obvious > pro/cons that I'm missing? > > > Thanks in advance! > -- 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/ec82c0ca-4e87-4582-97e9-2478c63dd5f7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
