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.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot