-
Bug
-
Resolution: Fixed
-
Major
-
None
Git polling not detecting changes since 1.1.1.
Seems to be related to "Excluded Users" feature.
Reverting to 1.0.7 fixed the issue.
Am getting in the git polling log the following:
Started on Jul 30, 2013 2:21:29 PM Using strategy: Default [poll] Last Built Revision: Revision AAA (origin/master) Fetching changes from the remote Git repositories Fetching upstream changes from origin Polling for changes in Ignored commit BBB: Found excluded author: Build System Done. Took 0.21 sec No changes
BBB is the SHA ID of a new commit that shouldn't be ignored.
- is duplicated by
-
-
- Open
-
[JENKINS-19001] Git polling not detecting changes since 1.1.1
Moosh Ben
created issue -
Moosh Ben
made changes -
| Component/s | New: git-client [ 17423 ] | |
| Component/s | Original: pollscm [ 17336 ] |
Moosh Ben
made changes -
| Assignee | Original: Vincent Latombe [ vlatombe ] | New: Nicolas De Loof [ ndeloof ] |
Christian Lövsund
added a comment - We get the same with following log:
Started on Aug 12, 2013 9:21:51 PM
Polling SCM changes on master
Using strategy: Default
[poll] Last Built Revision: Revision 730e90c26c960e878b4497ac1821061cf68f0166 (origin/master)
Fetching changes from the remote Git repositories
Fetching upstream changes from origin
Polling for changes in
Ignored commit 4fd36ecb850160d3f39f32ced3100deb1a42b043: Found excluded author: jenkins
Done. Took 2.4 sec
No changes
Christian Lövsund
added a comment - We get the same with following log:
Started on Aug 12, 2013 9:21:51 PM
Polling SCM changes on master
Using strategy: Default
[poll] Last Built Revision: Revision 730e90c26c960e878b4497ac1821061cf68f0166 (origin/master)
Fetching changes from the remote Git repositories
Fetching upstream changes from origin
Polling for changes in
Ignored commit 4fd36ecb850160d3f39f32ced3100deb1a42b043: Found excluded author: jenkins
Done. Took 2.4 sec
No changes
Jason Michael
added a comment - Same issue here, with the same logs:
Started on Sep 8, 2013 12:07:06 AM
Polling SCM changes on master
Using strategy: Default
[poll] Last Built Revision: Revision 338c0231f863070f3db37a2d2b7dcbec42801426 (origin/integration)
Fetching changes from the remote Git repositories
Fetching upstream changes from origin
Polling for changes in
Ignored commit e7612e9a8d83638c6ab931859fc6850713451301: Found excluded author: Jenkins CI
Done. Took 2.7 sec
No changes
If I look at the repo on github, I can verify that the author of that commit is not Jenkins CI (though the previous few are):
jlmichael authored 24 minutes ago 1 parent fe9a106 commit e7612e9a8d83638c6ab931859fc6850713451301
It's almost like it's considering only the first of perhaps several commits since its last built revision, and if that is from an excluded user, it doesn't check any of the more recent commits.
Jason Michael
added a comment - Same issue here, with the same logs:
Started on Sep 8, 2013 12:07:06 AM
Polling SCM changes on master
Using strategy: Default
[poll] Last Built Revision: Revision 338c0231f863070f3db37a2d2b7dcbec42801426 (origin/integration)
Fetching changes from the remote Git repositories
Fetching upstream changes from origin
Polling for changes in
Ignored commit e7612e9a8d83638c6ab931859fc6850713451301: Found excluded author: Jenkins CI
Done. Took 2.7 sec
No changes
If I look at the repo on github, I can verify that the author of that commit is not Jenkins CI (though the previous few are):
jlmichael authored 24 minutes ago 1 parent fe9a106 commit e7612e9a8d83638c6ab931859fc6850713451301
It's almost like it's considering only the first of perhaps several commits since its last built revision, and if that is from an excluded user, it doesn't check any of the more recent commits. 
Gautam Jayaprakash
added a comment - Does anyone know if this is still an issue with builds > 1.0.7? I've been holding off upgrading because of this problem...
Gautam Jayaprakash
added a comment - Does anyone know if this is still an issue with builds > 1.0.7? I've been holding off upgrading because of this problem... I think this has been fixed in 1.4 and was due to a bug computing changelog. Please reopen if this still occurs
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Christian Lövsund
added a comment - Still get the exact same thing after updating to 1.4.5 Christian Lövsund
made changes -
| Resolution | Original: Fixed [ 1 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
We ran into this issue too. In our case we had multiple excluded usernames in various formats at least one was an email address and one name had a space in it. Removing all but one entry with no special characters or spaces seemed to fix this issue.