You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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