manbetx客户端打不开私人赛跑者卡在npm安装 [英] GitLab private runner stuck on npm install

查看:330
本文介绍了manbetx客户端打不开私人赛跑者卡在npm安装的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试使用私人跑步者而不是共享跑步者在GitLab.com上设置CI管道。该项目使用Node,所以我使用的是 node:6 图片。

I'm trying to set up a CI pipeline on GitLab.com using a private runner instead of a shared one. The project uses Node, so I'm using a node:6 image.

.gitlab-ci.yml 看起来像这样:

image: node:6

stages:
    - test

javascript_tests:
    stage: test
    script:
        - npm install
        - npm run test:unit
    when: always

跑步者在跑步阶段停留大约30分钟,然后才开始输出相关内容:

The runner stays on "running" stage for about 30 minutes and only then started to output something relevant:

npm ERR! fetch failed 
http://10.252.156.164:4880/@types%2fjsforce/-/jsforce-1.9.2.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 10.252.156.164:4880

该怎么办?我以为在DigitalOcean Droplet上安装 gitlab-runner 是唯一要担心的事情。

What can I do to solve this? I thought that installing gitlab-runner on a DigitalOcean droplet would be the only things to worry about.

推荐答案

node:latest 替换 node:6 可以解决此问题。

Replacing node:6 with node:latest fixed this problem.

这篇关于manbetx客户端打不开私人赛跑者卡在npm安装的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆