Strategy: Inverse fails to prevent unwanted builds

This issue is archived. You can view it, but you can't modify it. Learn more

ExportXMLWordPrintable

      I've two jobs: myproject and myproject-master

      The first job is supposed to build all commits that land in master. It does its job admirably. The second job is supposed to build all other branches except master. For that purpose, I configured it as follows:

         <scm class="hudson.plugins.git.GitSCM" plugin="git@2.4.0">
...
     <branches>
       <hudson.plugins.git.BranchSpec>
         <name>master</name>
       </hudson.plugins.git.BranchSpec>
     </branches>
...
     <extensions>
       <hudson.plugins.git.extensions.impl.BuildChooserSetting>
         <buildChooser class="hudson.plugins.git.util.InverseBuildChooser"/>
       </hudson.plugins.git.extensions.impl.BuildChooserSetting>
     </extensions>
...
   </scm>
...
   <triggers>
     <com.cloudbees.jenkins.GitHubPushTrigger plugin="github@1.14.0">
       <spec></spec>
     </com.cloudbees.jenkins.GitHubPushTrigger>
   </triggers>
   <concurrentBuild>false</concurrentBuild>

      What happens when I push a branch "foo": myproject-branch builds it.

      What happens when I push the master branch: myproject-branch wakes up, fetches upstream changes, then says this:

      Seen 98 remote branches
No new revisions were found; the most-recently built branch will be built again.

      and proceeds to build an unrelated branch.

      What I expect: myproject-branch builds nothing.

            Assignee:
            Unassigned
            Reporter:
            Marius Gedminas
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: