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

Automatic Dependency Plugin triggers builds for all branches


We have 270 project, so managing manual dependencies is problematic. For this reason we have configured for each project Maven Dependency Processor and checked Automatic Dependency Management. Bamboo version: 6.2.9

Our projects in trunk have always x-SNAPSNOT version and project in branch never reference those snapshots, only some other versions. From maven perspective there is no connection between branch and trunk.

After enabling auto dependencies everything was working fine for some days, but today for no obvious reason auto generated dependencies are containing all branches. Now if we build trunk it triggers all branches, so basically nothing is working anymore, because all agents are working on every possible branch....

In build results in branch I can click on parent plan (child of) that has triggered this build, and after some time going up the parent tree i end up on project in trunk, and I can see in automatically generated  dependencies on this project, that it really is referencing this particular lib in branch. So definitely builds from trunk are triggering branches.

Before enabling automatic dependencies we've been managing them manually and this has been working fine for few years, and we never had such problem, that build in trunk would trigger one in branch.

I have some questions:

1) Should I see in Plan Configuration in Dependencies section also branches?

2) Is Maven Dependency Processor reliable, or maybe we should go back to manual dependencies management?

3) Can we fix it somehow? I mean, that trunk builds does not trigger branches. 

4) How can this happen, that such auto dependencies to branches can be generated at all?

1 answer

0 votes


We are on 6.8.0 and Bamboo specs helps and cover and minimise the manual work



Gonchik Tsymzhitov

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events