Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

When using tag triggers, how do I find out which repository triggered the build?

I have a plan which is triggered by someone pushing a tag to the master branch. Now I want to use this plan with multiple repositories, but for certain scripts within the pipeline to work I need to know during build time which repository triggered this specific build.

When using ${} I can only choose one of the repositories which are configured in the plan but this is static information, so it might not be the one which actually triggered the current build.

I found this but it only seems to work if you're using a repository trigger. With the tag trigger, the repository contents have not changed.

Is there any way to do this?

1 answer

Hello @Julia Valder 

I am working on a similar problem, for me, the tag trigger is not even working for multiple repositories. Could you share how you made it work for the multiple repositories?


I am working on a task where we create a new release branch for the repository that pushed a release tag on their master branch. It works for a single repository but not for multiple repositories.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events