Pollscm trigger runs the job twice for the same commit

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Unassigned
            Reporter:
            Shat Shabaev
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: