patternMinor
This job is stuck because you don't have any active runners online
Viewed 0 times
thisactiveyourunnersstuckanyonlinebecausejobhave
Problem
I try to use Gitlab-CI and create the runner, but when jobs start, the job with the needed runner doesn't start:
But this runner exists in the list:
How to use a runner?
And an additional question: all works fine with the "automatic" runner when I only create
But this runner exists in the list:
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?Solution
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.
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.
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.
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.
Context
StackExchange DevOps Q#12866, answer score: 3
Revisions (0)
No revisions yet.