runs-on not working for any runner

[Michał]

Why the following not working

runs-on:
  - self.hosted

I want to run on any self hosted so what is the problem that the runner cannot be found?

[Mark C]

Hi @Michał

Thanks for reaching out to the community.

Could be related to indentation about the config, could you try the below config instead?

pipelines:
  default:
    - step:
        runs-on: self.hosted
        script:
          - some_script_here

Regards,
Mark C

[Anwesha Pan]

Hi @Michał 👋🏻

Thanks for your question. 

It looks like your syntax isn't working because Bitbucket Pipelines does not use the generic self.hosted label. Instead, it uses a custom or system-assigned label matching system. If a runner is offline, unregistered, or the label is misspelled, the pipeline will fail to locate it.

You do try the following options:

1. Use the correct runner label
   Replace - self.hosted with the exact label assigned to your runner during setup (e.g., - self.hosted-linux, - windows, or a custom tag)
   
   
2. Check the label in Bitbucket
   • Go to your Repository or Workspace Settings.
   • Click on Settings -> Pipelines -> Runners. 
   • You must use one of these exact strings in your bitbucket-pipelines.yml file.
     
     
3. Verify Runner Status
   Your pipeline will throw an error if the runner is in an Offline status. Ensure that the machine hosting the runner is powered on and that the runner application is actively running in the terminal or as a service

For more details on configuring your custom runner environments, you can visit the Bitbucket Configure Runner Guide.

I hope this helps & resolves your issue. 🙂

Thanks,
Anwesha