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

Polling fails in "node on demand" environments

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • p4-plugin
    • None
    • Jenkins version 1.575
      P4 plugin version 1.0.12

      When you restrict your project to run against a specific label and all the nodes in that label are setup to go online/offline on demand, the polling log contains the following when all nodes are offline:

      Perforce Software Polling Log

      Started on Sep 5, 2014 2:49:00 AM
      We need to schedule a new build to get a workspace, but deferring 1,229,335ms in the hope that one will become available soon (all_suitable_nodes_are_offline)
      Done. Took 0.17 sec
      No changes

      I'm guessing this meaning that the polling was not done. Right?

          [JENKINS-24604] Polling fails in "node on demand" environments

          Michael Rose created issue -
          Mark Waite made changes -
          Link New: This issue is related to JENKINS-24529 [ JENKINS-24529 ]

          Elliot Wiltshire added a comment -

          Hi Michael,

          I don't believe the (Perforce plugin) polling would happen in this case, since the build is failing fairly high up the chain. Could you please tell me which version of Jenkins you're running? Also, if you trigger a build manually does it work properly?

          Thanks,
          -e.

          Elliot Wiltshire added a comment - Hi Michael, I don't believe the (Perforce plugin) polling would happen in this case, since the build is failing fairly high up the chain. Could you please tell me which version of Jenkins you're running? Also, if you trigger a build manually does it work properly? Thanks, -e.

          Michael Rose added a comment -

          Hi ewiltshi,

          Yes, manual triggers do work.

          Version information:
          Jenkins version 1.575
          P4 plugin version 1.0.12

          Thanks
          Michael

          Michael Rose added a comment - Hi ewiltshi , Yes, manual triggers do work. Version information: Jenkins version 1.575 P4 plugin version 1.0.12 Thanks Michael

          Elliot Wiltshire added a comment -

          Hi Michael,

          Thanks for checking those for me. It looks like this issue is with the Jenkins core, and not the Perforce plugin itself, based on your version information and this related (grandparent) ticket: https://issues.jenkins-ci.org/browse/JENKINS-22750

          There are a couple workarounds suggested there, which I hope will be of some help.

          -e.

          Elliot Wiltshire added a comment - Hi Michael, Thanks for checking those for me. It looks like this issue is with the Jenkins core, and not the Perforce plugin itself, based on your version information and this related (grandparent) ticket: https://issues.jenkins-ci.org/browse/JENKINS-22750 There are a couple workarounds suggested there, which I hope will be of some help. -e.

          Elliot Wiltshire added a comment -

          Not a defect in the Perforce plugin - this looks like it's an issue with the Jenkins core.

          Elliot Wiltshire added a comment - Not a defect in the Perforce plugin - this looks like it's an issue with the Jenkins core.
          Elliot Wiltshire made changes -
          Assignee New: Elliot Wiltshire [ ewiltshi ]
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

          Michael Rose added a comment -

          The issue you referenced say the problem was resolved in 1.565, but I'm running 1.575 and still seeing it. I'm guessing this b/c the Perforce plugin does use a workspace when polling which they said they weren't going to address. So basically (if I'm summarizing that issue right) Perforce polling will not work for a completely node on demand environment, I have to keep atleast one node running at all times.

          Michael Rose added a comment - The issue you referenced say the problem was resolved in 1.565, but I'm running 1.575 and still seeing it. I'm guessing this b/c the Perforce plugin does use a workspace when polling which they said they weren't going to address. So basically (if I'm summarizing that issue right) Perforce polling will not work for a completely node on demand environment, I have to keep atleast one node running at all times.

          Elliot Wiltshire added a comment -

          Although I do think this is related to the Jenkins core, and not the Perforce plugin itself, I'm re-opening this and will discuss with other developers. There may be a way to do an SCM poll without a workspace.

          Elliot Wiltshire added a comment - Although I do think this is related to the Jenkins core, and not the Perforce plugin itself, I'm re-opening this and will discuss with other developers. There may be a way to do an SCM poll without a workspace.
          Elliot Wiltshire made changes -
          Resolution Original: Not A Defect [ 7 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]

            p4paul Paul Allen
            mrose Michael Rose
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: