12

I'm using Gitlab's shared runner. Build has been in 'pending' state for over 20 minutes.

How to debug this? is it something to do with the runner availability or script execution issue.. Is it possible to gain more insight by any means?

enter image description here

Sahas
  • 3,046
  • 6
  • 32
  • 53
  • Even if runner is not shared one this information is useful. – kyb Jan 16 '19 at 16:24
  • there's nothing within GitLab itself. You would need access to view the runner logs or monitoring for it. On GitLab.com, there are public dashboards to view performance such as https://dashboards.gitlab.com/d/ci-runners-main/ci-runners-overview – Arty-chan May 16 '20 at 00:01

1 Answers1

1

I don't think the UI supports viewing a shared runner's queue. However, this 'pending' state can be caused by things other than a queue.

Check the tags for that pipeline stage against the tags supported by the runners available to the runners activated for your project:

Screencap of Runners screen for a pipeline

Remember, tags can vary from stage to stage, so it's possible for the first few stages to work before your pipeline is blocked.

Gitlab-ci will indicate 'pending' when a runner cannot be found with tags matching a given stage.

Matt Alioto
  • 403
  • 2
  • 10
  • 3
    GitLab will show a message about a 'stuck' job if there are no runners able to run the job - tags don't match, etc. A job that is simply pending without a stuck message is simply waiting for runner capacity to become available. – Drew Blessing Sep 23 '19 at 16:18