Gitlab runner is stuck on pending

GitLab CI/CD
1

I’ve got two builds that are completely stuck:

https://git.coderouge.co/folatt/kraken/builds/148
https://git.coderouge.co/folatt/core/builds/147

Runner is local with a python:3.5 docker image.

Relevant discussion:

https://bbs.arkos.io/t/runner-problems/2281

2

What does the Runner Status say on Gitlab Admin page?

What do you see in the logs (gitlab-ctl logs, or the admin logs page).

If you are not the admin of git.coderouge.co then you will need to talk to the admin of that site.

There is no best runner. There is only the runner you need or don’t need. Do you really need to use a docker runner? If you’re having problems, why not get your initial private CI solution (with your own trusted code) on a shell runner?

3

If you are not the admin of git.coderouge.co then you will need to talk to the admin of that site.

I will.

Do you really need to use a docker runner?

The admin does it, so I should too.

4

So basically this kind of question is “Why doesn’t this work on your gitlab ci runner, dear admin?”. If you can’t figure it out by inspection, you’ll need help from someone who can run commands interactively on the ci-runner host machine.

Things you can check quickly:

  1. What tags are associated with your project? You might need to add or remove a tag to get your work built, which tags are up to your CI build-server-administrator.

  2. Is there a runner active that will accept your project?

The most likely thing is that there are zero runners active that will accept your project.

5

Thanks. The admin gave me a shared runner and it’s working now.