Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×We've migrated a lot of builds from Bamboo to Bitbucket Pipelines.
In order to keep our monorepo but have many parallel build pipelines for different parts of the repo we're using the atlassian/trigger-pipeline pipe extensively.
When viewing builds for a repository which is triggered by the pipe, it's really hard to find out which source build pipeline triggered the pipeline.
We could update each of our atlassian/trigger-pipeline usage to include a source repo/build variable but it would be a lot more consistent if this was a feature that came out of the box somehow
@Jon Bevan _Adaptavist_ hi. Thanks for your suggestion. We will think about how to implement this, and we will notify you, when this feature will become available.
Regards, Igor
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.