How to specify Git repository when firing Bamboo release task from Jira?

Hi there,

I would like to know the best practices for JIRA and Bamboo integration. At the moment we have Bamboo plan for releasing new version of our XY plugin. Because we have about 20 plugins, each of them is in individual git repository, we would like to share the very same Bamboo plan for each XY plugin we develop.

We are not able to figure out how we can set the git repository/s that is related to JIRA project.

We are using Jenkins at the moment, we have made JIRA plugin for ourselves where we can specify repository/s for each JIRA project, thus when we was firing Jenkins job, we could simply pick the repository that was listed in JIRA project, so Jenkins cloned/checked out specified repository.

So the question is quite simple, is there any way how to fire the same Bamboo plan from JIRA, but against different repositories? If so, how? If not, what are the best practices? I don't belive that you have to have separate plans for each repository or that you have to fire the job for all specified repositories within Bamboo plan.

Thank you for any help, Jan

1 answer

Well I'm aware of multiple repositories within one Plan, but how to force the plan to use desired repository? Let's say we have one Release Plan within Bamboo configured with 20 repositories. But each run of plan should be agains just one repository (which is related to the plugin we are releasing now). So the question is, how I force Bamboo to run the plan on repository, that is related to Jira project when I fire Release task from Jira itself?

To make things more clear. We need to share the same plan for many repositories, where the plan itself runs always agains just one of defined repository.

That makes no sense to me. Why would you like to do that? Build plan is for me for a specific package (product). Multiple plugins in your case are multiple products, that can be deployed (via deployment projects) to the same or different test machines. Why do you want to use the same plan instead of having multiple plans?

Well because we have the all the same system for building and testing mechanism for about 50 projects, and growing. It will be very hard to maintain such an amount of copies of the same logic. Maybe if there could be sort of plan templates (set of tasks), that could be used in plan, that is related to project, that could help. So anyway, there is no way how to avoid duplications in plans definitions? Thank you.

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

4,702 views 20 14
View question

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you