You can use a JobDSL statement in the Jenkinsfile in the root of your repo to generate other jobs. Those jobs wouldn't be triggered by subsequent repo changes, unless you add a call to them in your main Jenkinsfile - they also could be triggered on-demand, through replay, a cron ...
--- Matt On Thursday, May 18, 2017 at 9:38:28 AM UTC-5, David Aldrich wrote: > > Hi > > > > As the free-style Multi-Branch Project plugin is deprecated, I am > experimenting with the Multibranch Pipeline job type. > > > > With the Multi-Branch Project plugin it was possible to have multiple > multi-branch jobs. We took advantage of that and had multiple jobs to > build different executables in the repo and to run different regression > tests, with different polling periods. > > > > It seems that the Multibranch Pipeline supports only one build script per > repo, defined by the JenkinsFile in the root directory. > > > > This seems to me to be restrictive. What is the thinking behind it and is > it possible to define multiple multi-branch pipeline jobs per repo? > > > > Best regards > > > > David > > > -- 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/4b45b914-1cdf-4dfe-9076-330fea88798c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
