nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Access multiple Bitbucket repositories from a single Pipeline

Michael Atkinson

We currently have two repositories: one that contains the source code for our application, and another that contains scripts to build and deploy that application to the cloud (among other things). I want to set up two Pipelines: one in the application repo that simply triggers a Pipeline in the build repo upon commit to a specific branch, and another in the build repo that is triggered from the application repo and simply grabs the source from the application repo and executes the build process as normal. This is not a problem on our local machines, but it seems the only solution for Pipelines it to write a custom pipe that uploads the source to S3 (for example) in the application repo, and then pulls that same source down in the build repo. Is there anyway to use something like an app password to grant the build repo access to the application repo? Or is Pipelines just not the tool for this job?

Accepted answers

Theodora Boudale

Hi Michael,

It is possible to clone another repo in Pipelines. Instead of using app passwords, you can use SSH. The following blog post explains how you can set this up:

https://bitbucket.org/blog/cloning-another-bitbucket-repository-in-bitbucket-pipelines

We also have a pipe that can trigger a pipeline for a different repo:

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

You can use this in the yml file of the application repo in order to trigger a pipeline for the build repo. There is also a variable WAIT for the pipe that you can set to 'true' or 'false', depending on whether you want the pipeline in the application repo to wait for the pipeline in the build repo to complete or not.

I'm not sure if you're already aware of this pipe and if you are using it already, I thought I'd mention it just in case.

Please feel free to let me know if you have any questions.

Kind regards,
Theodora

All comments

Theodora Boudale

Hi Michael,

It is possible to clone another repo in Pipelines. Instead of using app passwords, you can use SSH. The following blog post explains how you can set this up:

https://bitbucket.org/blog/cloning-another-bitbucket-repository-in-bitbucket-pipelines

We also have a pipe that can trigger a pipeline for a different repo:

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

I'm not sure if you're already aware of this pipe and if you are using it already, I thought I'd mention it just in case.

Please feel free to let me know if you have any questions.

Kind regards,
Theodora

Michael Atkinson

This is exactly what I was looking for, thank you Theodora!

Theodora Boudale

You are very welcome Michael, I'm glad to have helped!

Sameeksha Chepe_7bc1e3

This is useful for the CI/CD I am setting up too. Thanks for this answer.

However, I need to trigger a pipeline from another repo and use the build created by this pipeline.

Will I be able to use 'artifacts' from the nested pipeline into the current pipeline which triggers the nested one?

James Merkle

If you require multiple repositories to be cloned, I would recommend disabling the automatic clone feature, and manually clone the repositories needed, especially if two repositories need to be "siblings", at the same directory level.

Add the following to the top of your YML file:

clone:
  enabled: false # do not perform a git clone into the build folder by default

Within your 'script' section, clone the repos necessary (power-shell environment):
'jack' is the "current repository", for which BITBUCKET_BRANCH environment will define the branch.

script:
 - env | sort
 - echo "Clone jack and jill repositories"
 - git clone -b $BITBUCKET_BRANCH --depth=1 git@bitbucket.org:my_id/jack.git # clone the branch requested
 - git clone --depth=1 git@bitbucket.org:my_id/jill.git

The result will be two repositories, 'jack', and 'jill', both in the build folder.
Using --depth=1 will limit history, allowing a faster clone process.

Matt Spuddy Quail

James' suggestion worked well for my usecase. Specifying clone.enabled: false and cloning the two repos into their own directories was particularly insightful.

I my case, I wanted to also be able to do a git push to the main repo. Following the advice in this documentation lead me to this procedure:

Use HTTP instead of the SSH (git) protocol.
Set the http proxy (which will authenticate upstream for you).
Set the name/email git config (I set them to the same values that Pipelines uses).
Set push.default to squelch a git warning.

script:
- git config --global http.proxy http://localhost:29418
- git clone --branch="${BITBUCKET_BRANCH}" --depth 1 
"${BITBUCKET_GIT_HTTP_ORIGIN}" jack
- git clone --depth 1 http://bitbucket.org/my_id/jill.git
- cd jack
- git config user.name bitbucket-pipelines
- git config user.email commits-noreply@bitbucket.org
- git config push.default simple
- date > timestamp.txt
- git add timestamp.txt
- git commit -m "[skip ci] update timestamp"
- git push

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

atl-gruland

bitbucket-pipelines