-
Bug
-
Resolution: Unresolved
-
Major
-
None
We are seeing a weird problem occasionally on our jenkins setup ver 1.627
git client 1.19
git plugin 2.4 on ubuntu machine.
I have a job configured to poll scm every 5 minutes
sometimes, when there is a change the job gets triggered twice
once with the relevant changes and the second time says "no changes"
- duplicates
-
JENKINS-17346 git project building twice every time new change committed
-
- Open
-
- is related to
-
JENKINS-17346 git project building twice every time new change committed
-
- Open
-
- relates to
-
JENKINS-45280 duplicate build triggered by same github push notification when there is long scm polling
-
- Open
-
-
JENKINS-37381 Two builds triggered when building on new ec2 slave
-
- Closed
-
Unfortunately the only thing that seems to work is either switching to hooks (which we can't do for reasons) or increase the time between polling. Of course, by increasing the time between polling, your builds will trigger less frequently. We have ours at about 1 hour, which means there could be a delay of up to 1 hour between the time someone commits and the time Jenkins picks it up. I really wish someone would fix this bug, but seeing as it has been around for over 3 years I don't think it will happen.