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
In my plan there are multiple repository , the build will have multiple task for each repository (Artifact creation). Trigger the build in case of any commit in a repository is easy but is there any way that I can get, which repository and branch triggered the build so that i can use some sort of condition to skip the task for( Artifact creation) for those repository, where no changes have been commited. I am trying to the use the conditional plugin to skip the task from running if i get the get the details from trigger.
What you are trying to achieve is hard to do in Bamboo, but I'll share the information I have in case it helps you moving forward.
To check which plan triggered the build you will need to compare the following variables:
There is a Community post with an example of a possible approach to compare those variables on a "Unix like" agent:
The problem is, when you have this information, you can't use it as a source informaion for the Conditional tasks for Bamboo plugin. That is because it only accepts default Bamboo variables. If you discover which repository triggered the plan by using a script task (as suggested in the above post), you won't be able to use this information to avoid the task from running.
I opened a feature request to help us with this scenario in the future:
You could use the script to compare the Bamboo variables and then inject a new variable in your build that would tell you which repository triggered the build
To follow this idea you would need to configure your artifact creation on a script task and check the variable you injected (with the repo trigger information) to decide if you should run the commands or not on your script.
There is another feature request that might interest you:
I encourage you to vote in both feature requests shared in this answer. They both could potentially help you and other customers facing similar needs.
I hope that helps! =]