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

"no such computer" error occurs during SCM Pulling

    Details

    • Similar Issues:

      Description

      I am attempting to use a pipeline build triggered by github webhooks along with the kubernetes plugin.  I am seeing the following error in all of my poll logs:

      [poll] Latest remote head revision on refs/heads/master is: f4065637e80be6789d6d16c59ceee2cfde7b7ba9 - already built by 5

      ERROR: no such computer jenkins-slave-s10fr-lj69d

      Done. Took 0.58 sec No changes

      Looking at the plugin code there is a cache of what the workspace node has been in the past:

      https://github.com/jenkinsci/workflow-api-plugin/blob/63e8ad0c271573f4bebc57fb0776b3fac4fccea9/src/main/java/org/jenkinsci/plugins/workflow/FilePathUtils.java#L115

      Here is the line of code where the error is originating from:

      https://github.com/jenkinsci/workflow-job-plugin/blob/01f9e9bf32452a9d2ed7fa1e0ef92303e991a0c6/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java#L593

      Note that a workspace is required for the poll due to my use of "Additional Behaviors -> Polling ignores commits in certain paths"

      Assuming that a computer is available is an invalid assumption in the cloud where nodes are ephemeral.   I haven't yet come up with a work-around for this issue, so I am currently blocked.

      Thank you for your help!

        Attachments

          Activity

          Hide
          abayer Andrew Bayer added a comment -

          Sam Van Oort - fwiw, if there's any possible resolution, it'd be to do what freestyle does (if I remember correctly) and kick off a build if polling requires a workspace but there isn't one available. Some polling options do always require a workspace, so that's what we've got to play with. shrug

          Show
          abayer Andrew Bayer added a comment - Sam Van Oort - fwiw, if there's any possible resolution, it'd be to do what freestyle does (if I remember correctly) and kick off a build if polling requires a workspace but there isn't one available. Some polling options do always require a workspace, so that's what we've got to play with. shrug
          Hide
          sporkthrower Gigi Jackson added a comment -

          We're running into this issue, although we're using the "polling ignores commits with certain message" additional behavior. I'm wondering if disabling lightweight checkout might be a work around. My understanding is that will cause the repo to be cloned on the master in order to get the Jenkinsfile. We use spot instances heavily for build agents, but master should always be up, and we'd definitely be willing to take the performance hit and do the comparison on a clone on master to get the build trigger behavior we want.

          Show
          sporkthrower Gigi Jackson added a comment - We're running into this issue, although we're using the "polling ignores commits with certain message" additional behavior. I'm wondering if disabling lightweight checkout might be a work around. My understanding is that will cause the repo to be cloned on the master in order to get the Jenkinsfile. We use spot instances heavily for build agents, but master should always be up, and we'd definitely be willing to take the performance hit and do the comparison on a clone on master to get the build trigger behavior we want.
          Hide
          jandhollander Jan D'Hollander added a comment -

          We have the same issue.

          Subscribing to this.

          Show
          jandhollander Jan D'Hollander added a comment - We have the same issue. Subscribing to this.
          Hide
          zmeggyesi Zalan Meggyesi added a comment -

          Turns out, I'm afflicted by the same problem as well. So I'm voting for some sort of resolution, even if it involves kicking off a build, no matter how short it is (in Kubernetes, spinning a VM up and down quickly is mostly acceptable).

          Show
          zmeggyesi Zalan Meggyesi added a comment - Turns out, I'm afflicted by the same problem as well. So I'm voting for some sort of resolution, even if it involves kicking off a build, no matter how short it is (in Kubernetes, spinning a VM up and down quickly is mostly acceptable).
          Hide
          balihb Balázs Hámorszky added a comment -

          allowing master nodes and putting this in the pipeline solved this for me:

              node('master') {
                  checkout scm
              }
          Show
          balihb Balázs Hámorszky added a comment - allowing master nodes and putting this in the pipeline solved this for me: node('master') { checkout scm }

            People

            • Assignee:
              Unassigned
              Reporter:
              wgorman Will Gorman
            • Votes:
              5 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated: