GitLab CI immediately passes without running anything on self hosted instance

How to Use GitLab
1

No matter what I try, my GitLab CI pipelines aren’t completing properly on my self-hosted instance, but does work on GitLab.com

Even something as simple as the following doesn’t work:

image: node:latest

cache:
  paths:
    - node_modules/

build:
  script:
    - echo "hello world";

On my self-hosted instance, this returns:

Running with gitlab-runner 11.3.1 (0aa5179e)
  on gitlab 39ddf575
Job succeeded

And on GitLab.com this returns:

Running with gitlab-runner 11.4.0~beta.748.gcde4a2d1 (cde4a2d1)
  on docker-auto-scale 72989761
Using Docker executor with image node:latest ...
Pulling docker image node:latest ...
Using docker image sha256:8672b25e842c4c36f9f75d7edf48844ad32af57cf40596f5f236ed6462f073ba for node:latest ...
Running on runner-72989761-project-8575899-concurrent-0 via runner-72989761-srm-1537994426-74c3830d...
Cloning repository...
Cloning into '/builds/JacobTheDev/new-site'...
Checking out b51dcb1e as master...
Skipping Git submodules setup
Checking cache for default...
FATAL: file does not exist                         
Failed to extract cache
$ echo "hello world";
hello world
Creating cache default...
WARNING: node_modules/: no matching files          
Uploading cache.zip to https://storage.googleapis.com/gitlab-com-runners-cache/project/8575899/default 
Created cache
Job succeeded

Any help in getting this figured out would be immensely appreciated.

2

Wow, think I figured it out. I had modified the settings for the runner to use docker instead of shell, and apparently that broke something. I set up a new runner and it appears to be working (tentatively).

1 Like