## TL;DR

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 The job is stuck because your runners have tags and your jobs don't.

## Fix

1. Follow these 4 steps to enable your runner to run without tags: Or set tags to your jobs.
   Expected: You get the expected result; the problem is gone.
2. For more info: Configuration of your jobs with .gitlab-ci.yml - Tags
   Expected: You get the expected result; the problem is gone.

## When to use

- You are dealing with this situation.
- The symptom matches: This job is stuck, because the project doesn't have any runners online assigned to it. Go to Runners page.

## When NOT to use

- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported per the linked source. Source: https://stackoverflow.com/questions/53370840/this-job-is-stuck-because-the-project-doesnt-have-any-runners-online-assign.

## Variant phrasings

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

## Why it happens

I am learning GitLab CI/CD. I installed GitLab and GitLab Runner from Officials. Whenever I run the pipeline during Maven build, the job gets stuck. I have a registered runner and it 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: pat

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://stackoverflow.com/questions/53370840/this-job-is-stuck-because-the-project-doesnt-have-any-runners-online-assigned