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

"No polling baseline - Changes found" causing runaway polling

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • p4-plugin
    • Jenkins 2.138.3 (Windows on AWS EC2, both Master and Nodes)
      Blue Ocean 1.8.4
      P4 Plugin: 1.9.2

      I have a build job that polls Perforce for changes every 5 minutes. Occasionally, with (seemingly) no changes, Jenkins still start building the project every time it polls, regardless of whether there are new checkins or not. I call this "runaway polling".

      If I disable the build and then re-enable it after everything has finished, the runaway polling stops. However, this quickly overwhelms our Jenkins instance, as we allow concurrent builds.

      In the Perforce polling log, this message correlates to the problem. I see it in every "runaway polling" build:

      no polling baseline in D:\workspace\jobName on NODE_NAME
      Done. Took 7.2 sec
      Changes found
      

      Neither the node nor its p4 client are new, both have been in place for days. There's no indication what command is being run to check the "baseline", nor is there any information on why it starts failing, so this is very difficult to troubleshoot.

          [JENKINS-55737] "No polling baseline - Changes found" causing runaway polling

          Karl Wirth added a comment -

          Hi jazzyjayx. Thanks for letting us know. I tried to contact you directly by email because I'd like to get more information about the problem job. If you haven't received an email from me, please let me know.

          Karl Wirth added a comment - Hi jazzyjayx . Thanks for letting us know. I tried to contact you directly by email because I'd like to get more information about the problem job. If you haven't received an email from me, please let me know.

          Have been noticing the same in our Jenkins instance running p4 plugin 1.8.10.

          Deepu Sudhakar added a comment - Have been noticing the same in our Jenkins instance running p4 plugin 1.8.10.

          Karl Wirth added a comment -

          Hi deepu_s. Can you let me know if the error you see is related to the Jenkins master or Jenkins slave.

          Karl Wirth added a comment - Hi deepu_s . Can you let me know if the error you see is related to the Jenkins master or Jenkins slave.

          Karl Wirth added a comment -

          Karl Wirth added a comment - Fixes have been submitted in mainline (not released yet): https://swarm.workshop.perforce.com/changes/25439 https://swarm.workshop.perforce.com/changes/25437

          Jay Spang added a comment -

          This seems to be fixed now. It has not reprod since 1.9.7 was installed.

          Jay Spang added a comment - This seems to be fixed now. It has not reprod since 1.9.7 was installed.

          Karl Wirth added a comment -

          Hi jazzyjayx, Thanks for letting us know. I'll shut this bug for now, but if it does come back please feel free to reopen it.

          Karl Wirth added a comment - Hi jazzyjayx , Thanks for letting us know. I'll shut this bug for now, but if it does come back please feel free to reopen it.

          Karl Wirth added a comment -

          Karl Wirth added a comment - Fixed in 1.9.7: https://swarm.workshop.perforce.com/changes/25439 https://swarm.workshop.perforce.com/changes/25437

            p4karl Karl Wirth
            jazzyjayx Jay Spang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: