Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-38443

Pollscm trigger runs the job twice for the same commit

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: core, pipeline
    • Labels:
      None
    • Environment:
      Jenkins 2.7.4
    • Similar Issues:

      Description

      We've got the job with pollscm trigger enabled for two repositories.
      The job is triggered twice with one minute interval, though both commit hashes are the same.

      Pollscm logs look like this:

      Started on Sep 22, 2016 9:47:00 AM
      Using strategy: Default
      [poll] Last Built Revision: Revision <revA> (go/master)
      ...
      [poll] Latest remote head revision on refs/heads/master is: <revA> - already built by 1
      Using strategy: Default
      ...
      [poll] Latest remote head revision on refs/heads/master is: <revB>
      Done. Took 1 sec
      Changes found
      
      Started on Sep 22, 2016 9:48:00 AM
      Using strategy: Default
      [poll] Last Built Revision: Revision <revA> (go/master)
      ...
      [poll] Latest remote head revision on refs/heads/master is: <revA> - already built by 2
      Using strategy: Default
      ...
      [poll] Latest remote head revision on refs/heads/master is: <revB>
      Done. Took 0.65 sec
      Changes found
      

      <revA, revB> pair is the same in two job runs.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ifn Shat Shabaev
              • Votes:
                5 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: