GitLab CI builds remains pending

Question

We recently started to use GitLab-CI on the gitlab.com free service. At first everything went fine, but now, seems like we can't build our project anymore. The builds are shown as pending and doesn't do anything.

Here's what we have in our builds list:

And if we check the details of a build:

As you might notice, in the list, each build is assigned to a runner id, but in the details page, the runner section is blank.

At first, we thought it was just latency caused by gitlab.com ingrastructure, but it's really just stuck there...

EDIT

It's more than 1 year ago but I keep having notifications about this question. If I recall properly, the problem was due to GitLab itself. Follow the GitLab docs and make sure your setup is valid, and hope for the best !

would https://github.com/gitlabhq/gitlab-ci/issues/64#issuecomment-75379083 help? — VonC, Jan 06 '16 at 05:31
We don't use a self-hosted gitlab, we're using the one provided by gitlab.com — Pascal Boutin, Jan 06 '16 at 05:53
@PascalBoutin I think it's important you update your question to add that extra bit of info from your comment — ympostor, Feb 28 '17 at 06:03

score 25 · Answer 1 · answered Jun 30 '20 at 18:15

25

If you are working with local gitlab-runner, like macOS or custom runner that you have been made, you should start running jobs manually.

Based on this topic on gitlab documentation you should start manually in user-mode or system-mode based on where you executing this command

Run in terminal

If you did not started gitlab-runner yet

gitlab-runner start

system-mode execution

sudo gitlab-runner run

user-mode execution

gitlab-runner run

answered Jun 30 '20 at 18:15

Mohammad Reza Koohkan

1,656
1
16
36

1

Thank you! I have my own gitlab-runner on a Linux server and I didnt understand why my jobs were stuck on pending. Starting the runner and actually RUNNING the jobs on the server was my solution. Now to find a way to make it run any job automatically :) – Maarten Apr 28 '21 at 11:36
1

as soon as your gitlab-runner become started jobs runs automatically. – Mohammad Reza Koohkan Jun 06 '21 at 14:58
1

Thank you!, I was stuck to this on mac, sudo gitlab-runner run worked for me – Abhinay Gupta Nov 12 '21 at 19:31

score 11 · Answer 2 · answered Aug 07 '19 at 10:44

I was stuck into same issue on my windows machine. I went to event viewer to get some logs of the service and found the error "listen_address not defined".

I followed below steps to fix it.

Go to gitlab repository and edit the runner settings.
You will find checkbox named "Indicates whether this runner can pick jobs without tags"
Make sure the option is checked.

It works for me now.

score 7 · Answer 3 · answered Oct 02 '21 at 16:51

My problem was solved after doing the following steps:

Go to your project repository, click on CI/CD and then select pipelines. Try removing the runner cache by clicking on clear runner caches.
Verify, start and run your local runners by the doing the following steps on the server you have registered your runners:
```
sudo gitlab-runner verify
sudo gitlab-runner start
sudo gitlab-runner run
```

score 5 · Answer 4 · edited Oct 15 '19 at 20:18

5

GitLab maxed out their shared runners but they have just finished adding more of them. Now GitLab has 12 shared runners. Take a look at this issue: https://gitlab.com/gitlab-org/gitlab-foss/issues/5543#note_3130561

Update

GitLab has moved to auto scaling Runners. If you're still hitting any issues it might be due to a different cause.

edited Oct 15 '19 at 20:18

Avior

481
6
18

answered Jan 06 '16 at 21:32

Jose Torres

1,025
11
21

FYI We currently have 18 shared runners. – Jose Torres Feb 15 '16 at 18:31
@JoseTorres do you work for GitLab? otherwise your answer is confusing; would be great if you could clarify that – ympostor Feb 28 '17 at 06:01
@ympostor yes, good point. I've edited the answer so it can stand on it's own. – Jose Torres Mar 26 '17 at 17:05

score 1 · Answer 5 · answered Apr 07 '21 at 14:55

1

Try to clear the Runner cache if you have set it up.

Goto CI/CD>>Pipelines>>on top side >> clear Runner Caches

answered Apr 07 '21 at 14:55

Ranganath Vaishnav

11
1

score 1 · Answer 6 · answered May 04 '22 at 18:14

1

For me, this workaround worked: Pausing and unpausing the runner triggers the pending job to run.

Reference: https://gitlab.com/gitlab-org/gitlab/-/issues/23401

answered May 04 '22 at 18:14

leodotcloud

1,830
14
15

score -2 · Answer 7 · answered Jan 20 '23 at 15:50

-2

I had the same issue because there were no active runners.

Go to settings > CI CD > Enable shared runners for this project

answered Jan 20 '23 at 15:50

Sidney Sousa

3,378
11
48
99

GitLab CI builds remains pending

7 Answers7

Run in terminal

Update

Linked