Re: Match multiple branches with Git plugin

[Mark Waite]

You didn't mention the type of job you're using.

If you're using a Freestyle job, it should work exactly as you desire, detecting changes on all the branches that match the wildcard.  It works that way for me on several jobs that I use.  A Freestyle job processing multiple branches tends to confuse users, since they need to look deeply into the job to decide which branch was used on each build.  It is less and less common to use a Freestyle project that builds multiple branches.

If you're using a Pipeline job, then you should consider using a Multibranch Pipeline job rather than reusing the same job for different branches.  A multibranch Pipeline job will automatically create and delete jobs for all branches that are detected and contain a Jenkinsfile.

On Thu, Sep 19, 2019 at 7:33 AM Technical Lead <chanse...@gmail.com> wrote:

Hi, I'm trying to use the Git plugin (with the GitHub plugin) to trigger builds on multiple branches with a single branch specifier rule.  However, the job only appears to trigger when there are changes to on the "first" matching branch.  I've tried wildcards (i.e. origin/dev/*) and regexes (i.e. :^origin/dev/.*), to no avail.  The limited documentation sort of indicates that the wildcard method would only use the first matching branch, but it's unclear for a regex.  I'd rather not reconfigure the job every time a new branch is added to list it explicitly in a branch specifier.

--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/76d496e6-edea-4ff9-b317-bdc69481f955%40googlegroups.com.

--

Thanks!

Mark Waite