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

Polling keeps building without changes on error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • p4-plugin
    • Jenkins 2.121.2, P4 1.8.15

      We've got a pipeline containing a shared library and multiple p4 checkout steps on different servers, with different p4 clients.

      Polling perforce detects changes and starts build.

      But if the build fails, the next polling step again changes are found, event though there are none and a new build is started, over and over again.

      The Polling Log shows:

       

      This page captures the polling log that triggered this build.Started on XXX
no polling baseline in D:\Jenkins\workspace\XXX@libs\shared-library on 
P4: Polling on: master with:XXX_Build
Found last change 1129035 on syncID XXX_Build
... p4 client -o XXX_Build
 +... p4 info
 +
P4 Task: establishing connection.
... server: perforce:1666
... node: XXX
P4: Polling with range: 1129035,now
... p4 changes -m20 //XXX_Build/...@1129035,now
 +P4: Polling on: master with:XXX_Package
Done. Took 0.56 sec
Changes found

      1129035 was the last change for our view and there are no new changes after this change. Any help on how to stop the Polling from thinking there are changes?

       

       

       

            p4karl Karl Wirth
            wouterslob Wouter Slob
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: