Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

refer a private repo from different workspace in pipeline.yml

dharun k September 8, 2025

Is it possible to refer a Bitbucket Private repo in Workspace-A in a bitbucket-pipeline.yml in Workspace-B

- pipe: *workspacename*/*repository-name*:v1.0.0

It throws me the below error. But when i change the Repo in Workspace-A to public it works. Any workarounds that can be used here? Apart from Dockerising the repo. 

Configuration error
It looks like you tried to use a pipe in your bitbucket-pipelines.yml that doesn’t exist. Check the name of the pipe and try againimage.png

1 answer

0 votes
Mark C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 10, 2025

Hi @dharun k

Welcome to the community.

Unfortunately, when using a Pipe, the repository should be public (see this doc for more info).

Apart from the Dockerising the repo, here are some alternatives to interact with another repository:

  • You can simply Git clone the repository and proceed
  • If you'd like to get a YAML configuration available from another repository, you can use shared Pipelines configurations
  • If you'd like to trigger a Pipelines build in another repository, you can use this Pipes script called trigger-pipeline

Regards,
Mark C

dharun k September 15, 2025
Thank you for your quick response.

I’m looking to implement the trigger-pipeline approach you mentioned. My goal is to use a pipe.yml from a different workspace(A) and repository within the pipeline.yml of another workspace’s (B) repository.


variables:
ATLASSIAN_ACCOUNT_EMAIL: 'my-email'
ATLASSIAN_API_TOKEN: 'token'
REPOSITORY: 'repo name'
ACCOUNT: 'workspace name'
REF_TYPE: 'branch'
REF_NAME: 'main'
WAIT: 'true'
 

But i still end up getting the below error. Really appreciate your input on this. 

✖ Account, repository or branch doesn't exist.


Note - Both Workspace and Repos are private
Mark C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 16, 2025

Hi @dharun k

Could you confirm if the branch name exists in the repo where you're trying to trigger a build?

Regards,
Mark C

dharun k September 16, 2025

Hi @Mark C 
Yes, I do have the repository along with the branch. 
Can you please let me know if you are available for a quick call to run through my setup?
this is my email - dharunk22@gmail.com

dharun k September 17, 2025

Hi @Mark C 
Kindly let me know your availability if we can have a quick run through of the above issue i am facing. Thanks in advance for your assistance on this. 

 

dharun k September 18, 2025

Hi @Mark C 
Any inputs on this please?
Thanks in advance for your help on this. 

 

Mark C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 19, 2025

Hi @dharun k

Could you try to enable the `DEBUG: 'true'` for the Pipes script? This will give more info about the error you're getting.

Regards,
Mark C

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events