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

"no such computer" error occurs during SCM Pulling

    XMLWordPrintable

    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
          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 }
          Hide
          intelmatt Matt G added a comment -

          Same issue here. I'd almost say it's a serious bug because it can result in a build not happening, even when there are changes in SCM. It can be quite bad if the job is only configured to send notification to developers after a build failure. People may think they are covered by CI, but in reality it is not building any of their changes. (This is what happened to us)

          Show
          intelmatt Matt G added a comment - Same issue here. I'd almost say it's a serious bug because it can result in a build not happening, even when there are changes in SCM. It can be quite bad if the job is only configured to send notification to developers after a build failure. People may think they are covered by CI, but in reality it is not building any of their changes. (This is what happened to us)
          Hide
          thompdre84 Drew added a comment -

          Same issue here as well. This bug is a blocker for us as we have a larger number of packages that are subdirectories in a single git repository. I tried to use "Polling ignores commits in certain paths", but this leads to the same error as OP. Is the only workaround to use the master node for these sorts of builds?

          Show
          thompdre84 Drew added a comment - Same issue here as well. This bug is a blocker for us as we have a larger number of packages that are subdirectories in a single git repository. I tried to use "Polling ignores commits in certain paths", but this leads to the same error as OP. Is the only workaround to use the master node for these sorts of builds?
          Hide
          alan_md Alan MD added a comment -

          Same issue here when using the EC2 dynamic agents. I opened another issue JENKINS-65199.
          Has anyone found a workaround?

          Show
          alan_md Alan MD added a comment - Same issue here when using the EC2 dynamic agents. I opened another issue  JENKINS-65199 . Has anyone found a workaround?

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            wgorman Will Gorman
            Votes:
            11 Vote for this issue
            Watchers:
            18 Start watching this issue

              Dates

              Created:
              Updated: