As Pipelines is repository-centric, we don't support this natively. Though there are a couple of setups you could use, depending on your use case.
The first is if you have dependent repositories. So if you have two things you release independently of each other, but you don't want to release if you've broken an integration point between them.
For this I'd suggest having your Repo #1 pipeline clone Repo #2 and then you can do your E2E testing there. (if both can potentially break the integration, you'd want to do the equivalent in both repositories). For details on how to set up cloning via SSH: https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-bitbucket-pipelines-847452940.html.
The second is if the repositories need to be built and deployed together.
In this case you could use sub repositories, and have your pipeline run on the combined repository.
Hopefully this helps.
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs