[JIRA] [git-plugin] (JENKINS-20607) GIT Plugin 2.0: Polling ignores commit from certain users not working

[cactus.jir...@gmail.com (JIRA)]

Title: Message Title

Sergio Roldan commented on JENKINS-20607   Re: GIT Plugin 2.0: Polling ignores commit from certain users not working I guess this is not the same issue when using Jenkins Workflow Plugin. I can see this git polling log: Started on Oct 15, 2015 9:08:29 AM Using strategy: Default [poll] Last Built Revision: Revision 74072d171ab432943380ab42ab14950a1149bb04 (refs/remotes/origin/develop) > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repositories > git config remote.origin.url g...@github.com:organization/project.git # timeout=10 Fetching upstream changes from g...@github.com:organization/project.git > git --version # timeout=10 using GIT_SSH to set credentials deploy user on github > git -c core.askpass=true fetch --tags --progress g...@github.com:organization/project.git +refs/heads/*:refs/remotes/origin/* Polling for changes in > git rev-parse refs/remotes/origin/develop^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10 > git log --full-history --no-abbrev --format=raw -M -m --raw 74072d171ab432943380ab42ab14950a1149bb04..bb7c4edad7fa934f5b67cdd7a24f8c42fd9f899f # timeout=10 Ignored commit bb7c4edad7fa934f5b67cdd7a24f8c42fd9f899f: Found excluded author: deployuser Ignored commit 3f417d8e3ae6e9c7e024a41d719cb08e7dba594f: Found excluded author: deployuser Using strategy: Default [poll] Last Built Revision: Revision 74072d171ab432943380ab42ab14950a1149bb04 (refs/remotes/origin/develop) using GIT_SSH to set credentials deploy user on github > git --version # timeout=10 > git -c core.askpass=true ls-remote -h g...@github.com:organization/project.git # timeout=10 Found 7 remote heads on g...@github.com:organization/project.git [poll] Latest remote head revision on refs/heads/develop is: bb7c4edad7fa934f5b67cdd7a24f8c42fd9f899f Done. Took 2.5 sec Changes found It is using git "user.name" because I have also tested with random users (ssh keys not related with any github user deploy keys ) setting an arbitrary user.name property. As you can see, 'deployuser' is detected and excluded in the first polling, but later, changes are detected and build is fired. Using same polling configuration from a free-style job works like a charm. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.