"Mark Waite" <mark.earl.wa...@gmail.com> wrote: > The multi-branch freestyle job type and the multibranch pipeline job type > will automatically create and delete a job for each branch that matches your > selection criteria. > I very much prefer a job per branch because it makes the changes easier to >read, and the history of test pass and fail much easier to understand. But multibranch pipeline is today not in a state where it is a usable replacement for other job types. No graphics displayed from the plugins, many plugins are not compatible and also some plugins are not on the list for compatibility like cubertura. We started to migrate one job to multibranch pipeline but we had no success to find enough workarounds. And it lacks a bit of documentation. I believe it is the way it should work and it is on track, but today it is not usable for production.
Regards Klaus -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-ab8b23ff-e262-45eb-a264-f143f03ae06c-1474352557694%403capp-gmx-bs30. For more options, visit https://groups.google.com/d/optout.