• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • git-plugin
    • Jenkins 2.73.2 (Docker image jenkins/jenkins:lts)
      Git Plugin 3.6.2
      Ubuntu 16.04 (64-bit) running Docker 1.12.6

      Project configured to poll Git with Branch Specifier "**" seems to detect changes that aren't there.

       

      Started on Oct 27, 2017 2:18:58 AM
      Polling SCM changes on [node_unavailable]
      Using strategy: Default
      [poll] Last Built Revision: Revision adaec1b1c0e4b83dab922eeb490b2f09a4839d30 (origin/EGN-1489)
      Done. Took 1 ms
      Changes found
      

      I then changed the Branch Specifier (and nothing else) to "master/origin" and it seems to be working fine.

       

       

       

      Started on Oct 27, 2017 5:13:55 PM
      Using strategy: Default
      [poll] Last Built Revision: Revision 9a027daf6d4fd437312b382a5dc7fdfebbb4c9b0 (origin/master)
      using GIT_SSH to set credentials 
       > git ls-remote -h ssh://git@adlm.nielsen.com:7999/em/nano.git # timeout=10
      Found 43 remote heads on ssh://git@adlm.nielsen.com:7999/em/nano.git
      [poll] Latest remote head revision on refs/heads/master is: 9a027daf6d4fd437312b382a5dc7fdfebbb4c9b0 - already built by 167
      Done. Took 0.74 sec
      No changes
      

      That doesn't build all my branches, though, so that's not really good. I changed it back to "**" and polling now produces the same aberrant behavior as before:

       

       

      Started on Oct 27, 2017 5:23:55 PM
      Polling SCM changes on [node_unavailable]
      Using strategy: Default
      [poll] Last Built Revision: Revision 9a027daf6d4fd437312b382a5dc7fdfebbb4c9b0 (origin/master)
      Done. Took 1 ms
      Changes found
      

      The log of the checkout shows it's checking out the head revision of origin/master and rebuilding it needlessly.

      I've looked, and it doesn't appear I have any weird branch names that seemed to have been trouble in other reports.

       

       

      f1b18914d6bdff17899c71852c17502c0a7087be refs/heads/BARB2016
      8bdfbb9135414029f12ccad803105a4be602c8ab refs/heads/BLE-EA-integration
      56da67b503ad63ce49149da38b859a932c0baef1 refs/heads/EA-Wifi-Integration
      a6a8073570834fc892443fa2fd3adebbcdbe17e3 refs/heads/EGN-1242
      2f9ac80b3bce81c00879a14f6840e835ec83bfa9 refs/heads/EGN-1384-reenable-all-disabled-unit-tests
      915a336838fd95ba133544bfa53b96b9e1ab8e45 refs/heads/EGN-1385-migrate-jenkins-and-build-scripts
      ce4f8b08867ea75bb3811583e340fb7151183980 refs/heads/EGN-1392-automation-support-nano-people-meter
      cd8fc999ad0ddde40c44d609807ad5966607faf3 refs/heads/EGN-1413
      3646dd17db882cec0d7d37a42caa74826e4e6fe9 refs/heads/EGN-1414
      407475b8633ac8f58789804a7d7842c883a2804e refs/heads/EGN-1417
      7db43e26eba24d9a9f5f601d7e24ee78a9a5b067 refs/heads/EGN-1419
      5b9bef4ebcc416187b9fd196612630db1342ac17 refs/heads/EGN-1443-improve-wifi-scan
      b982b795572f8e21e0f852f2e215cafb48d9eb59 refs/heads/EGN-1475-change-wifi-timer-from-3-seconds
      fc791f30552062a7d1504cb464bdacf513f8efba refs/heads/EGN-1477
      7468635991f27575338f035639d27c40c77ecf7c refs/heads/EGN-1480
      6e184050922d83cd8102f6984c24b1ba9e083bbb refs/heads/EGN-1488
      adaec1b1c0e4b83dab922eeb490b2f09a4839d30 refs/heads/EGN-1489
      f8e886d0e008fa159d250b33db89e8c2f61545c4 refs/heads/EGN-1491-digital-to-analog-converter-dac
      ca177a99d561d2bd3d3245a0b0792f7b153957b0 refs/heads/EGN-1492
      a2f0673fb8b97c51f47a3df809cee4c4157a92e2 refs/heads/EGN-1494
      69cf160d4c731ac87d0b311da4e9632e30d49463 refs/heads/EGN-1503
      cb09390915f6f917dc74bc6e3394cf4758173faa refs/heads/EGN-1521
      a712f92c33a3e95ab0ebc28c24c52e3c380fe167 refs/heads/EGN-1532
      ac6604b02b42bbf84eab92b01f2f2f9f0f516000 refs/heads/EGN-1534
      a51fade2a29bc0ccef9388b7b382c89ab65e0e19 refs/heads/EGN-1547
      d0e6a0020bcc4d43b72938ce0110cd8cd8ca0903 refs/heads/EGN-599-firmware-upgrade-fails-occasionally
      c0bc6299ce5c2cd2ef48ae4c05123a9d0dcde83d refs/heads/EGN-669
      87ff62daa25cab5efc49a2c96dff355607a218a1 refs/heads/EGN-797
      c8b7c38fafe8619f698126d0c92161a9742181c9 refs/heads/EGN-822
      a346f3c736d686e620b89c503d782a87139d324a refs/heads/Sprint20
      29b37b4eb3290a1fd541b06769151f7a34c335f0 refs/heads/WolfSSL
      7db43e26eba24d9a9f5f601d7e24ee78a9a5b067 refs/heads/bugfix/EGN-1421
      95addbeba0685994962e1c55bf81e5767a883cb1 refs/heads/bugfix/EGN-1422
      366be9450cdf07dcb6f00cde1d0b562f4122c4e0 refs/heads/bugfix/EGN-1424-person-in-events-is-not-getting
      5fa5825a62ed3a25b993d3d673025351593a2a29 refs/heads/feature/EGN-1373-research-and-report-usb-cable-unplugged
      e462be94e659da14ebbed131628cadb8c1d49bec refs/heads/feature/EGN-1374-automation-support-led-test-cases
      5fa5825a62ed3a25b993d3d673025351593a2a29 refs/heads/feature/EGN-232-cycle-the-battery-regularly
      9a027daf6d4fd437312b382a5dc7fdfebbb4c9b0 refs/heads/master
      a5e4899e1a78ae8bab7f031979e167db6bc46c8e refs/heads/nano_ea_int1
      6f6091e7bb76a7cf4b6ff7526fc92f9b66225416 refs/heads/x.0.16
      308ca3ad8e2f523c10eeb1545346381528f4570a refs/heads/x.1.26
      088ee0aea109d7435e9396fbbabd11830e900d55 refs/heads/x.1.27
      57cc56efbff0dd4edbb2fdd5988eb43b39a24ed4 refs/heads/x.1.28
      

       

          [JENKINS-47701] Git Poll Detects Spurious Changes

          Paul Braman added a comment -

          Note that the suggestion to "force polling using workspace" does not resolve the issue.

          Paul Braman added a comment - Note that the suggestion to "force polling using workspace" does not resolve the issue.

          Paul Braman added a comment -

          There was also a suggestion to use reference repositories which doesn't work. The polling happens outside the use of any reference repository.

          Paul Braman added a comment - There was also a suggestion to use reference repositories which doesn't work. The polling happens outside the use of any reference repository.

          Paul Braman added a comment - - edited

          Adding a note that I also tried triggering a build on "any new tag" by setting the refspec to "+refs/tags/*:refs/remotes/origin/tags/*" and the branch specifier to "*/tags/*". When initially kicked off, the job properly churned through all of the existing tags and kicked off a build for each of them. However, it still detected changes after it had built the last tag and simply repeated the build for the last tag it had built until I disabled the job.

           

          If I could figure out where it persists its information, maybe I can figure out why it's repeating the same thing?

          Paul Braman added a comment - - edited Adding a note that I also tried triggering a build on "any new tag" by setting the refspec to "+refs/tags/*:refs/remotes/origin/tags/*" and the branch specifier to "*/tags/*". When initially kicked off, the job properly churned through all of the existing tags and kicked off a build for each of them. However, it still detected changes after it had built the last tag and simply repeated the build for the last tag it had built until I disabled the job.   If I could figure out where it persists its information, maybe I can figure out why it's repeating the same thing?

          Paul Braman added a comment -

          Adding another note:

          I had "origin/master" building fine in a project. I added a new branch "origin/branchname" and the system continually rebuilds the second branch even though there are no updates in Git. So, one project with two individual branches listed (but no wildcards) still causing problems.

          Paul Braman added a comment - Adding another note: I had "origin/master" building fine in a project. I added a new branch "origin/branchname" and the system continually rebuilds the second branch even though there are no updates in Git. So, one project with two individual branches listed (but no wildcards) still causing problems.

          David D added a comment -

          this happens random on one of my tasks with polling.
          sometimes it just keeps saying found changes and kicks off a build. (my task set to 15min polling interval)

          • yesterday afternoon, removed the scm-polling.log file under the task, then it fixed the problem
          • this morning, there is a commit, triggered a build, but then it started keep building, even no change in repo...

          hope this can be fixed, or someone could explain how jenkins determines a change? does it compare the sha1 in scm-polling.log and the one from polling? 

          thanks.

          David D added a comment - this happens random on one of my tasks with polling. sometimes it just keeps saying found changes and kicks off a build. (my task set to 15min polling interval) yesterday afternoon, removed the scm-polling.log file under the task, then it fixed the problem this morning, there is a commit, triggered a build, but then it started keep building, even no change in repo... hope this can be fixed, or someone could explain how jenkins determines a change? does it compare the sha1 in scm-polling.log and the one from polling?  thanks.

          Edie Zhang added a comment -

          I have the same issue.

          I think the problem is the poll determine the changes against the previous build commit id. If branch filter is '**', then the changeset is calculated against random branches(from the previous build).

          Hope there is a way to specify the particular branch to calculate the changeset during poll.

          Edie Zhang added a comment - I have the same issue. I think the problem is the poll determine the changes against the previous build commit id. If branch filter is '**', then the changeset is calculated against random branches(from the previous build). Hope there is a way to specify the particular branch to calculate the changeset during poll.

            Unassigned Unassigned
            bramankp Paul Braman
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: