'This job is stuck, because the project doesn't have any runners online assigned to it. Go to Runners page

I am learning CI/CD.

I have installed Gitlab And Gitlab Runner From Officicals. But whenever running the pipeline during maven-build, the job gets stuck. I have registred runner and is available to my project but jobs get stuck

.gitlab-ci.yml

image: docker:latest
services:
- docker:dind

variables:
 DOCKER_DRIVER: overlay
 SPRING_PROFILES_ACTIVE: gitlab-ci

stages:
- build
- package
- deploy

maven-build:
 image: maven:3-jdk-8
 stage: build
 script: "mvn package -B"
 artifacts:
 paths:
  - target/*.jar

docker-build:
stage: package
script:
 - docker build -t registry.com/ci-cd-demo .
 - docker push registry.com/ci-cd-demo

k8s-deploy:
 image: google/cloud-sdk
 stage: deploy
 script:
  - echo "$GOOGLE_KEY" > key.json
  - gcloud container clusters get-credentials standard-cluster-demo -- 
  zone us-east1-c --project ascendant-study-222206
   - kubectl apply -f deployment.yml

My Runner Settings

Error message while runner already associated with project

Please help?

Solution 1:^[1]

The job is stuck because your runners have tags but your jobs don't. Follow these 4 steps to enable your runner to run without tags:

Or set tags to your jobs. For more info: Configuration of your jobs with .gitlab-ci.yml - Tags

Solution 2:^[2]

Make sure you are using the correct tag i.e. whatever present corresponding to the configured runner for your project.

In your case it would be like :

maven-build:
 image: maven:3-jdk-8
 stage: build
 tags: my project ci-cd
 script: "mvn package -B"
 artifacts:
 paths:
  - target/*.jar

Solution 3:^[3]

Also you can tag your jobs using the following syntax in file .gitlab-ci.yml:

stages:
  - check
  - build
  - test
  - analyze
  - package
  - release
  - deploy
nohttp:
  stage: check
  tags:
    - dev

Besides not to forget to add tag "dev" to your project's specefic/shared runner.

Solution 4:^[4]

It was quite simple on my side, I just run gitlab-runner run on my computer

Solution 5:^[5]

In my case i had to modify the tags in the admin area from 'Tag1, Tag2' to 'Tag1,Tag2'. Spaces caused my issue.

Solution 6:^[6]

As far as I know, it is not possible for a normal user to check if the shared runners available on a gitlab server are set to only run tagged jobs or not.

I suggest that gitlab add this to information about runners in the CI/CD settings page for projects, i.e. which runners are available, which tags they run AND whether they only run tagged jobs.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1
Solution 2	Armel
Solution 3	Mohsen Abasi
Solution 4	Mohamed Dernoun
Solution 5	user480355
Solution 6	Kári Harðarson

'This job is stuck, because the project doesn't have any runners online assigned to it. Go to Runners page

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]