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

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-20607 
 
 
 
  GIT Plugin 2.0: Polling ignores commit from certain users not working  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Assignee:
 
 Nicolas De Loof 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

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

[winner...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andy Wang commented on  JENKINS-20607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GIT Plugin 2.0: Polling ignores commit from certain users not working  
 
 
 
 
 
 
 
 
 
 
Mark Waite I tested on a small job without Gerrit-trigger plugin. And the result showed that the polling ignores are well functioning. I tested on all three ignore commit options( by user name, by commit message and by file path), they all worked no matter if the "Force polling using workspace" checked or not.  But once added Gerrit-trigger plugin, it didn't work. The job triggers on all commits despite the polling ignore settings. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

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

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-20607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GIT Plugin 2.0: Polling ignores commit from certain users not working  
 
 
 
 
 
 
 
 
 
 
Andy Wang you might consider creating a small test job which does not use the Gerrit-trigger plugin, just to see if you can confirm that you're using the correct syntax for excluding by user name. Once it is functioning in the simple job, then try that same syntax with your job which uses the Gerrit-trigger plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

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

[winner...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andy Wang commented on  JENKINS-20607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GIT Plugin 2.0: Polling ignores commit from certain users not working  
 
 
 
 
 
 
 
 
 
 
Hitting the issue and the workaround doesn't work for me. Using Jenkins ver. 1.635; Git plugin 2.4.0; Gerrit-trigger plugin 2.17.0 I set both ignore commit from certain users and in certain paths. But neither worked. How do people deal with it when it relates to change version number in certain file and don't want that to trigger a build? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

[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 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
   

[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 edited a comment 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:{code}Started on Oct 15, 2015 9:08:29 AMUsing strategy: Default[poll] Last Built Revision: Revision 74072d171ab432943380ab42ab14950a1149bb04 (refs/remotes/origin/develop) > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repositories > git config remote.origin.url g...@github.com:organization/project.git # timeout=10Fetching upstream changes from g...@github.com:organization/project.git > git --version # timeout=10using 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=10Ignored commit bb7c4edad7fa934f5b67cdd7a24f8c42fd9f899f: Found excluded author: deployuserIgnored commit 3f417d8e3ae6e9c7e024a41d719cb08e7dba594f: Found excluded author: deployuserUsing 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=10Found 7 remote heads on g...@github.com:organization/project.git[poll] Latest remote head revision on refs/heads/develop is: bb7c4edad7fa934f5b67cdd7a24f8c42fd9f899fDone. Took 2.5 secChanges found{code}It is using git "user.name" because I have also tested with random users ( deploy 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) 
 
 
 
 
  
 
 
 
  

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

[ductuyenl...@yahoo.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tuyen Lieu commented on  JENKINS-20607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GIT Plugin 2.0: Polling ignores commit from certain users not working  
 
 
 
 
 
 
 
 
 
 
I tested again with additional "Use commit author in changelog" behaviour. It returned my author name < Lieu, Tuyen> 

 

 @Override
public Boolean isRevExcluded(GitSCM scm, GitClient git, GitChangeSet commit, TaskListener listener, BuildData buildData) {
String author = commit.getAuthorName();
if (getExcludedUsersNormalized().contains(author)) {
// If the author is an excluded user, don't count this entry as a change
listener.getLogger().println("Ignored commit " + commit.getCommitId() + ": Found excluded author: " + author);
return true;
}

return null;
}
 

 
As you can see from the method above, without the "Use commit author in changelog", it will return author name. In my case, it returns author name with/without this option, which seems quite strange. I guess Stash may notify some funny metadata. 
Have you tried to put some breakpoints at the above method in hudson.plugsin.git.extensions.impl.UserExclusion ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

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

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-20607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GIT Plugin 2.0: Polling ignores commit from certain users not working  
 
 
 
 
 
 
 
 
 
 
Sergio Roldan your comment that it does not work for the workflow case is a very different case than the case described in this bug. I'm not sure the workflow use of the git plugin enables all the configuration options available in the git plugin, especially things that are as complicated as excluding commits by user. I think you'd be better served by reporting a separate bug, rather than just including a comment in this bug report. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

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

[ductuyenl...@yahoo.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tuyen Lieu commented on  JENKINS-20607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GIT Plugin 2.0: Polling ignores commit from certain users not working  
 
 
 
 
 
 
 
 
 
 
I got the same issue with : Jenkins ver. 1.609.3 Git plugin ver 2.4.0 
Build job gets triggered by all the commits, even though I specify the username, message,path to be excluded. I tried the workaround above yet It doesn't work. 
Any idea ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

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

[ductuyenl...@yahoo.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tuyen Lieu edited a comment on  JENKINS-20607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GIT Plugin 2.0: Polling ignores commit from certain users not working  
 
 
 
 
 
 
 
 
 
 Alright,After debugging, I found out the root cause:In case of ignoring the username , actually ,jenkins using  string ,it's not your git username ,but the profile lastname firstname, (I am using Stash). So let's say my Git (Stash) username is abc, my firstname is Tuyen, my lastname is Lieu:TO make it work ignoring the commit from my username, put this : Tuyen Lieu.In case of message, from the source code, it turns out to be that Jenkins automatically add "\n" to the end of the comment. i.e :"this is my comment" (stash) will be like "this is my comment\n" when jenkins parses the commit metadata.So to correct this, add "\n" to your pattern :  "  .*[this]\n.*    "   Hope it helps. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

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

[ductuyenl...@yahoo.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tuyen Lieu commented on  JENKINS-20607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GIT Plugin 2.0: Polling ignores commit from certain users not working  
 
 
 
 
 
 
 
 
 
 
Alright, 
After debugging, I found out the root cause: In case of ignoring the username , actually ,jenkins using  string ,it's not your git username ,but the profile lastname firstname, (I am using Stash). So let's say my Git (Stash) username is abc, my firstname is Tuyen, my lastname is Lieu: TO make it work ignoring the commit from my username, put this : Tuyen Lieu. 
In case of message, from the source code, it turns out to be that Jenkins automatically add "\n" to the end of the comment. i.e : "this is my comment" (stash) will be like "this is my comment\n" when jenkins parses the commit metadata. So to correct this, add "\n" to your pattern : .[this]\n.  
Hope it helps. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

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

[ductuyenl...@yahoo.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tuyen Lieu edited a comment on  JENKINS-20607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GIT Plugin 2.0: Polling ignores commit from certain users not working  
 
 
 
 
 
 
 
 
 
 Alright,After debugging, I found out the root cause:In case of ignoring the username , actually ,jenkins using  string ,it's not your git username ,but the profile lastname firstname, (I am using Stash). So let's say my Git (Stash) username is abc, my firstname is Tuyen, my lastname is Lieu:TO make it work ignoring the commit from my username, put this : Tuyen Lieu.In case of message, from the source code, it turns out to be that Jenkins automatically add "\n" to the end of the comment. i.e :"this is my comment" (stash) will be like "this is my comment\n" when jenkins parses the commit metadata.So to correct this, add "\n" to your pattern : ". \ *[this]\n. \ * "Hope it helps. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

[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  
 
 
 
 
 
 
 
 
 
 
Using current last versions of plugins ( git 2.4.0 and git-client 1.19.0 )  
 

It works in a free-style job (commits ignored by user name)
 

It doesn't work in a workflow job ( https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin version 1.10 ) using Workflow Script from SCM
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

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

[hube...@gmail.com (JIRA)]

 
Hubert S
 edited a comment on  JENKINS-20607


GIT Plugin 2.0: Polling ignores commit from certain users not working
















This works with:
GIT Client 1.16.1
GIT plugin 2.3.5
Jenkins 1.580.1

What caught me is the syntax of the config. I was only putting in the email, and it turns out I need to be far more explicit.

For instance, my Git commit username is:

"First Last first.l...@example.org"


For the Jenkins config field, I added:
"First Last"
"First Last first.l...@example.org"

For this to start working.






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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.

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

[hube...@gmail.com (JIRA)]

Hubert S
 commented on  JENKINS-20607


GIT Plugin 2.0: Polling ignores commit from certain users not working















This bug was not fixed with JENKINS-19001.

This still occurs with:
GIT Client 1.16.1
GIT plugin 2.3.5
Jenkins 1.580.1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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.