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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,553,049
Community Members
 
Community Events
184
Community Groups

Identifying which repository was updated in Trigger

Edited

Hello,

 

I have a bamboo plan that contains around 20 different repositories.  

I have configured a trigger to monitor all of those repositories and kick off the Job if it detects any changes to the master branch on any of those repositories.

Inside of the job, I was hoping there was a way for me to identify which repository was changed, as I want to pass that as a value to my script that runs.

The only option I see for this in the documentation is calling a variable like - 

${bamboo.planRepository.<position>.name}

 

Unfortunately, since the trigger monitors 20 repositories, this isnt helpful since I wont know what the position of the repo that was updated was (since it could be any one of them).

Is there another way to get the name of the repository that had an update pushed to it when it is in a list other repos in the same trigger?

 

Thanks.

1 answer

Use conditionals maybe and then use the I below variable to do a check?

bamboo_planRepository_#_name

  

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events