Thanks Jeremy. Our developers already have control of their projects'
branches' Jenkinsfiles so they can define whatever triggers/schedule they
want. If I were going to hack this, I'd probably prefer to do the opposite
of what you're recommending. Since git scanning is a wheel already invented
You could leave the Automatic triggering suppressed and write a tool to
scan your GIT repo looking for new branches and trigger the build via an
API call when a new branch is found. Sounds like you might need such a tool
anyway so that developers could schedule builds.
On Thursday, September 1
1. I have a multibranch pipeline job that takes 30min to run, has a lot of
branches, and my company is still at the earlier stages of devops
transformation, so with our current infrastructure we do not want to
trigger a build every commit.
2. Our job pipeline uses parameters heavily, so I would
