Is it possible to access multiple repositories from a self-hosted pipeline?

[Kaspar Vibur]

I have a self-hosted pipeline runner and from there I would like to run another pipeline that relies on the same self-hosted runner. Is that possible? 
If yes, following the guide trigger-pipeline guide:

https://bitbucket.org/product/features/pipelines/integrations?p=atlassian/trigger-pipeline

What should I specify as "pipe:" value?

[Patrik S]

Hello @Kaspar Vibur and thank you for reaching out to Community!

If you only have one runner available, and the second pipeline would rely on the same runner, it would not be possible.

This is because each runner can run only one pipeline step at a time, meaning that the first pipeline would already be making the runner "busy", and once it triggers the second pipeline, there will be no available runner to assign it.

However, if you create and spin up more than one runner (you can execute multiple runners in the same host, or use different hosts), then you should be able to achieve the workflow you are looking for. Following is an example of using the pipe in a step with runners : 

- step:
       runs-on:
        - 'self.hosted'
        - 'linux'
       script:
        - echo "This step runs in a self hosted runner"
        - pipe: atlassian/trigger-pipeline:5.2.0
          variables:
            REPOSITORY: '<string>'

Hope that helps! Let me know in case you have any questions.

Thank you, @Kaspar Vibur !
Patrik S

[Kaspar Vibur]

Thank you @Patrik S for your reply! I had set up a separate runner for the other repository but once I got the configuration correct I was presented with the following:

Configuration error

The Pipes feature is not supported on this self-hosted runner's platform.

So that I belive answers the question for my self-hosted MacOS runner.

My binary app project compiles sources from multiple repositories and as far as I understand now the only option to compile using pipeline would be to clone those other repositories into the runner.

[Patrik S]

Hello @Kaspar Vibur ,

It seems like you are using MacOS runners, and pipes are currently supported only on Linux Docker runners, as they rely on docker containers to properly work (see Unsupported feature | MacOS Runners)

In this case, you can either call the API to Run the pipeline directly in your step's script: 

• Run a pipeline | Bitbucket Cloud API

or, as you mentioned, manually clone the other repositories you need during your build.

Thank you, @Kaspar Vibur !

Patrik S