<p>After Further research, I found <a href="https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3750" rel="nofollow noreferrer">an open issue on gitlab</a> pretty similar to mine.
They describe runners freshly created and unable to pick up jobs.
As for my use case, The runner was created but with warning stating &quot;New Runner, has not connected yet&quot;.</p>
<p>In order to further check the status of the runner, I went to my terminal on the machine where I installed and registered the runner, namely my mac book pro, and I ran the following command:</p>
<pre><code>sudo gitlab-runner verify
</code></pre>
<p><a href="https://i.sstatic.net/zYWy6.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/zYWy6.png" alt="enter image description here" /></a></p>
<p>In the settings of the project, the runner's status switches to &quot;<strong>Online</strong>&quot; as you can see below, with a green label:</p>
<p><a href="https://i.sstatic.net/2QIZc.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/2QIZc.png" alt="enter image description here" /></a></p>
<p>As a result, the project's pipeline status went from &quot;Pending&quot; to &quot;Running&quot;</p>
<p><a href="https://i.sstatic.net/zldkt.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/zldkt.png" alt="enter image description here" /></a></p>
<p>Nevertheless, while the change of pipeline status, from &quot;pending&quot; to &quot;running&quot; thanks to gitlab runner's status going &quot;Online&quot;, the associated CI build Job Status is still stuck at &quot;Pending&quot;. This means that gitlab runner, even with all its characteristics looking fine, fails to pick up the job he's supposed to.
<a href="https://i.sstatic.net/ZaKpB.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/ZaKpB.png" alt="enter image description here" /></a></p>
<p>I'm aware this is not really a pure answer with final solution but I hope this will help move things forward on this topic !</p>

CC BY-SA 4.0
2021-05-19T20:57:50.617Z
Hi @phgolard, while this may lead to more research, information into this particular issue, this is not a constructive answer for this question. I would recommend if you would like to post this answer as a separate question if it is something you are looking to gain answers on.
Preston Martin
CC BY-SA 4.0
2021-05-20T22:14:14.980Z
@PrestonMartin thanks a lot for your advice. I am sorry while I've been "consuming" stackoverflow for a very long time, this is one of my first posts. You are right that I would be happy to get some answers/reactions on that, but intuitively I put it as an answer to the initial question since this is how things happened: I asked the question, I made further investigations which I found relevant so I shared them to move things forward and I did not know what would be the best: replying to my own question or creating a new one with additional pieces of information. I'll take note of this! Thx
phgolard
CC BY-SA 4.0
2021-05-20T23:38:10.443Z
While starting a new question may be the right answer, it is also fine to append additional research to your existing question.  An edit will send it to the top of the main page and usually get you some extra eye balls that you didn't have before.
chicks
CC BY-SA 4.0
2021-05-15T12:14:57.977Z
2021-05-15T12:36:57.420Z
2021-05-15T12:36:57.420Z
phgolard
<p>Runners are machines (typically containers) where your jobs run. Gitlab offers shared runners, and you can also bring in your own runners (machines that you register against Gitlab to run your jobs).</p>
<p>The main difference between Gitlab shared runners and the ones you bring is that the shared runners are, well, shared, so sometimes you have to wait for a bit for a job to start. You can also bring more powerful machines so that your jobs run faster.
You can find some docs on runners <a href="https://docs.gitlab.com/runner/" rel="nofollow noreferrer">here</a>.</p>
<p>In your case it seems that the runners have a problem, looking at the exclamation sign next to the name, which should be a green ball. Maybe hovering over the sign will give you some clues into what's happening.</p>

CC BY-SA 4.0
2020-12-04T15:59:10.583Z
2020-12-04T15:59:10.583Z
migueldavid
<p>I try to use Gitlab-CI and create the runner, but when jobs start, the job with the needed runner doesn't start:</p>
<p><a href="https://i.sstatic.net/kmyvp.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/kmyvp.png" alt="enter image description here" /></a></p>
<p>But this runner exists in the list:</p>
<p><a href="https://i.sstatic.net/clFKb.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/clFKb.png" alt="enter image description here" /></a></p>
<p>How to use a runner?</p>
<p>And an additional question: all works fine with the &quot;automatic&quot; runner when I only create <code>.yml</code> file. Why do I need to create some other runners and why runners needed?</p>

<gitlab-ci-runner>
This job is stuck because you don't have any active runners online
Valentyn Hruzytskyi
# This job is stuck because you don't have any active runners online

(Asked by: username_0 on 2020-11-26)

I try to use Gitlab-CI and create the runner, but when jobs start, the job with the needed runner doesn't start:

[![enter image description here](https://i.sstatic.net/kmyvp.png)](https://i.sstatic.net/kmyvp.png)

But this runner exists in the list:

[![enter image description here](https://i.sstatic.net/clFKb.png)](https://i.sstatic.net/clFKb.png)

How to use a runner?

And an additional question: all works fine with the "automatic" runner when I only create `.yml` file. Why do I need to create some other runners and why runners needed?

**Tags:** gitlab-ci-runner


---

## 2 answers

### Answer by username_4 on 2020-12-04. Score: 3 | Accepted answer

Runners are machines (typically containers) where your jobs run. Gitlab offers shared runners, and you can also bring in your own runners (machines that you register against Gitlab to run your jobs).

The main difference between Gitlab shared runners and the ones you bring is that the shared runners are, well, shared, so sometimes you have to wait for a bit for a job to start. You can also bring more powerful machines so that your jobs run faster.
You can find some docs on runners [here](https://docs.gitlab.com/runner/).

In your case it seems that the runners have a problem, looking at the exclamation sign next to the name, which should be a green ball. Maybe hovering over the sign will give you some clues into what's happening.


---

### Answer by username_1 on 2021-05-15. Score: 3

After Further research, I found an open issue on gitlab pretty similar to mine.
They describe runners freshly created and unable to pick up jobs.
As for my use case, The runner was created but with warning stating "New Runner, has not connected yet".
In order to further check the status of the runner, I went to my terminal on the machine where I installed and registered the runner, namely my mac book pro, and I ran the following command:
sudo gitlab-runner verify


In the settings of the project, the runner's status switches to "Online" as you can see below, with a green label:

As a result, the project's pipeline status went from "Pending" to "Running"

Nevertheless, while the change of pipeline status, from "pending" to "running" thanks to gitlab runner's status going "Online", the associated CI build Job Status is still stuck at "Pending". This means that gitlab runner, even with all its characteristics looking fine, fails to pick up the job he's supposed to.

I'm aware this is not really a pure answer with final solution but I hope this will help move things forward on this topic !

> **Comments:**
> **username_2**: Hi @username_1, while this may lead to more research, information into this particular issue, this is not a constructive answer for this question. I would recommend if you would like to post this answer as a separate question if it is something you are looking to gain answers on.  
> **username_1**: @PrestonMartin thanks a lot for your advice. I am sorry while I've been "consuming" stackoverflow for a very long time, this is one of my first posts. You are right that I would be happy to get some answers/reactions on that, but intuitively I put it as an answer to the initial question since this is how things happened: I asked the question, I made further investigations which I found relevant so I shared them to move things forward and I did not know what would be the best: replying to my own question or creating a new one with additional pieces of information. I'll take note of this! Thx  
> **username_3**: While starting a new question may be the right answer, it is also fine to append additional research to your existing question.  An edit will send it to the top of the main page and usually get you some extra eye balls that you didn't have before.  

---

