I've found the documentation, here:
I am hoping to understand exactly what criteria are used to decide when to add or remove build plan dependencies.
I have many instances of build plans where my understanding of the system indicates that there should be a dependency, but there is none listed on the Dependencies tab in the plan config, and many instances of build plans where my understanding indicates there should be no dependency, but one exists. Furthermore, sometimes a build is triggered as a result of another build as if a dependency were present, but none is.
We have dozens of shared libraries, many of which have dependencies on other libraries, and dozens of services using these libraries. All of these are built with Bamboo and Maven 3. All have the Dependency Check task configured and the checkbox checked as described in the documentation.
As noted in the subject, I'm looking for a thorough explanation. But I also have some specific questions:
If it makes a difference, we are using the locally hosted variety of Bamboo. We're currently on version 5.13.2 and are actively investigating an upgrade to 6.x.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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!
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