Bitbucket pipeline steps being queued indefinitely with runners

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Cloud のみ - この記事は、 クラウド プラットフォームのアトラシアン製品にのみ適用されます。

 

要約

Bitbucket Pipelines builds that run on self-hosted runners can sometimes remain in a queued state indefinitely. This issue can occur even when there are other runners available to accept new connections.

環境

Bitbucket Cloud Pipelines

原因

This issue may arise due to a communication failure between the Runners and the backend of Bitbucket Pipelines. In some rare instances, the Runner will fail to reach Bitbucket to confirm the current Runner status, causing a desync between the two.

回避策

Delete the existing runner. 

  1. Go to the repository preferences
  2. Navigate to Runners to access the runner settings page.
  3. Select the runner that needs to be deleted and click on the three dots.
  4. Choose Delete.
  5. Create a new runner

ソリューション

If prefer to maintain your existing runner, raise a ticket with Bitbucket Cloud Support and provide us with the "RUNNER_UUID" or a HAR file when loading the runner settings page.

How to get the Runner UUI

The Runner UUID is now available on the Pipeline build, as demonstrated in the example below: 

Pipelines build details:

Runner matching labels:
    - linux
    - self.hosted
Runner name: test3
Runner UUID: {0b72dd80-8656-5770-8c23-bfccf28be744}
Runner labels: self.hosted, linux
Runner version:
    current: 1.433
    latest: 1.433


Our engineering team can then update the backend for this specific runner to make it available again.

How to get runner UUID 

  • Identify the runner that is available but not being assigned any pipeline steps. 
  • From the "docker container run" command which pipelines provides when you create your runner there would be a field showing something as below : 

    RUNNER_UUID={9221374-acbd-574d-be9b-7c112gt526c1b}




最終更新日: 2024 年 1 月 2 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.