On Thu, Jul 21, 2016 at 11:42 AM, alex kessinger <voidfi...@gmail.com> wrote:
> I've tried the seed job-dsl method previously. Some automation was better > then no automation, but I think the Jenkinsfile in repo is even better. If > I make a change to the Jenkinsfile, that change can be isolated in each > environment/branch until it has been promoted to next step. If I have one > master seed job it's harder for me to control the promotion between > environments. > I agree, being able to have multiple Jenkinsfiles or specify multiple jobs in one definitely feels like the right and superior option. I suppose you could work around it by having your Jenkinsfile only run on master (either via an option in the job or by checking env.BRANCH_NAME in the Jenkinsfile), and then that Jenkinsfile runs job-dsl, which creates Pipeline jobs that run for every branch/PR as desired. But, it will probably be organizationally inferior and everyone will be having to reinvent some logic to create and organize these sub-jobs that should be maintained in one place. -- 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/CADya-sZwfJSZuOL1cJRz7Zv%2BMyU2-5%2BmG7QmBF%3DzYzPGsitwuw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
