Pipeline is stuck on "pending"

Question

I'm using GitLab's shared CI runners for training. Since this morning I can't build my project because the pipeline's status is "pending".

Is it because the number of shared runners is maxed out ? Too busy running other people's code ?

Is there a setting I need to check ? I know I can pay for a dedicated runner but I'm not in commercial setting at this point therefore I'm sticking with shared ones.

Thank you for assistance.

can you please check if pipeline is waiting for some resource? The default timeout is set to 1 hr so it should be failed by now. Can you please check and share the logs and update above? — Arihant Godha, Dec 14 '20 at 14:12
@ArihantGodha It is running now again. From the looks of it I just had to wait as shared runners are used by many for training. — wood, Dec 14 '20 at 14:34

score 1 · Answer 1 · answered Dec 14 '20 at 14:42

In such situations I would highly recommend to make the best use of tags. You can use tags to select a specific runner from the list of all runners that are available for the project.

In this example, the job is run by a runner that has both ruby and postgres tags defined.

job:
  tags:
    - ruby
    - postgres

If you have your own runners setup then you can use tags to run different jobs on different platforms. For example, if you have an OS X runner with tag osx and a Windows runner with tag windows, you can run a job on each platform:

windows job:
  stage:
    - build
  tags:
    - windows
  script:
    - echo Hello, %USERNAME%!

osx job:
  stage:
    - build
  tags:
    - osx
  script:
    - echo "Hello, $USER!"

If this is still a problem then consider using your own private runner.

Pipeline is stuck on "pending"

1 Answers1