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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.