Triggering child builds with Bamboo automatic dependencies

[David Moles]

We've configured Bamboo to use automatic dependencies based on Maven POM files. This appears to be working, insofar as the Bamboo interface correctly shows which the Maven artifacts required by and created by each plan, which upstream plans provide the dependencies and which downstream plans depend on the artifacts.

However, it also appears to not work, insofar as building an upstream artifact doesn't trigger a downstream build. Is it necessary to manually create child plans to trigger downstream builds -- an error-prone duplication of the information in the POM files? If so, the automatic dependency management isn't much use and it's hard to understand what the feature is for.

[Pawel Skierczynski]

First thing to check is if version that downstream build depends on is SNAPSHOT and if version that upstream builds is the same SNAPSHOT. It works only for SNAPSHOTS.

[David Moles]

Everything is 1.0-SNAPSHOT AFAICT.