Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28149

"Excluded Users" option doesn't work with multiple branches specified in "Branch Specifier"

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • git-plugin
    • None
    • jenkins ver: 1.589
      git plugin: 2.3.5

      I specified two branches separately in "Branch Specifier" option as below:
      Branch Specifier(blank for 'any'): */master
      Branch Specifier(blank for 'any'): */develop

      I also specified two Excluded users under the "Polling ignores commits from certain users' option, show as following:
      Excluded Users:
      James
      Kobe

      Then when James push his changes to either */master or */develop branches, jenkins would still trigger a build, same happened with user Kobe, which is unreasonable.

      Based on my understanding, jenkins should not trigger a build since both James and Kobe are whithin the excluded user list. This is definitely a bug, hope someone will fix it soon, thank you all!

          [JENKINS-28149] "Excluded Users" option doesn't work with multiple branches specified in "Branch Specifier"

          Huluwa added a comment -

          add additional information:
          I am using GitBucket as a git server and configured it to trigger build once push detected by setting the webhook in the git repository.

          Huluwa added a comment - add additional information: I am using GitBucket as a git server and configured it to trigger build once push detected by setting the webhook in the git repository.

          Mark Waite added a comment -

          I was able to duplicate this bug. When multiple branches are monitored, commits from one of the excluded users seem to only be ignored on one of the two branches, but not on both the branches.

          Mark Waite added a comment - I was able to duplicate this bug. When multiple branches are monitored, commits from one of the excluded users seem to only be ignored on one of the two branches, but not on both the branches.

          Huluwa added a comment -

          Here are the steps to make this defect easier to reproduce:

          Step1:Setup 2 Branch Specifier:
          Branch Specifier(blank for 'any'): */master
          Branch Specifier(blank for 'any'): */develop

          Step2: Setup 1 Excluded User:
          James

          Step3: Configure your jenkins job to be triggered by Git webhook.

          Step4: From your laptop, make sure the user name specified in your .git/config is James. And then push one commit to remote master branch, make sure this time your job doesn't triggered run.

          Step5: Still from your laptop, make sure the user name specified in your .git/config is James. And this time push one commit to remote develop branch, you will see this time your job get triggered, which should not be.

          Huluwa added a comment - Here are the steps to make this defect easier to reproduce: Step1:Setup 2 Branch Specifier: Branch Specifier(blank for 'any'): */master Branch Specifier(blank for 'any'): */develop Step2: Setup 1 Excluded User: James Step3: Configure your jenkins job to be triggered by Git webhook. Step4: From your laptop, make sure the user name specified in your .git/config is James. And then push one commit to remote master branch, make sure this time your job doesn't triggered run. Step5: Still from your laptop, make sure the user name specified in your .git/config is James. And this time push one commit to remote develop branch, you will see this time your job get triggered, which should not be.

            Unassigned Unassigned
            neteaser007 Huluwa
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: