[JIRA] (JENKINS-46468) "no such computer" error occurs during SCM Pulling

3 views
Skip to first unread message

svanoort@cloudbees.com (JIRA)

unread,
Apr 12, 2018, 11:57:02 AM4/12/18
to jenkinsc...@googlegroups.com
Sam Van Oort commented on Bug JENKINS-46468
 
Re: "no such computer" error occurs during SCM Pulling

Andrew Bayer Would it make sense to reclassify this as an improvement?

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

svanoort@cloudbees.com (JIRA)

unread,
Apr 12, 2018, 11:57:02 AM4/12/18
to jenkinsc...@googlegroups.com

andrew.bayer@gmail.com (JIRA)

unread,
Apr 12, 2018, 12:01:06 PM4/12/18
to jenkinsc...@googlegroups.com
Andrew Bayer commented on Bug JENKINS-46468
 
Re: "no such computer" error occurs during SCM Pulling

Either that or close as a won't fix.

svanoort@cloudbees.com (JIRA)

unread,
Apr 12, 2018, 12:18:01 PM4/12/18
to jenkinsc...@googlegroups.com
Sam Van Oort updated an issue
Change By: Sam Van Oort
Issue Type: Bug Improvement

svanoort@cloudbees.com (JIRA)

unread,
Apr 12, 2018, 12:20:02 PM4/12/18
to jenkinsc...@googlegroups.com
Sam Van Oort commented on Improvement JENKINS-46468
 
Re: "no such computer" error occurs during SCM Pulling

Andrew Bayer Executing discretion here... it feels like this ought to be do-able in some way with enough cleverness without checking out to a build agent, but it's definitely not a bug. So reclassifying and dropping priority because it's kind of edge-casey and potentially complex as well.

svanoort@cloudbees.com (JIRA)

unread,
Apr 12, 2018, 12:20:02 PM4/12/18
to jenkinsc...@googlegroups.com

andrew.bayer@gmail.com (JIRA)

unread,
Apr 12, 2018, 12:25:02 PM4/12/18
to jenkinsc...@googlegroups.com
Andrew Bayer commented on Improvement JENKINS-46468
 
Re: "no such computer" error occurs during SCM Pulling

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

jjackson@zymergen.com (JIRA)

unread,
Oct 3, 2018, 7:48:02 PM10/3/18
to jenkinsc...@googlegroups.com

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.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jan.dhollander@gmail.com (JIRA)

unread,
Feb 13, 2019, 4:08:01 AM2/13/19
to jenkinsc...@googlegroups.com

We have the same issue.

Subscribing to this.

zmeggyesi@skawa.hu (JIRA)

unread,
Feb 21, 2019, 5:24:02 AM2/21/19
to jenkinsc...@googlegroups.com

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).

balihb@gmail.com (JIRA)

unread,
Oct 31, 2019, 7:48:03 AM10/31/19
to jenkinsc...@googlegroups.com

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

    node('master') {
        checkout scm
    }
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages