You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I set up two parent and child projects as described https://confluence.atlassian.com/bamboo/setting-up-plan-build-dependencies-289276887.html but Bamboo does not find parent dependencies in the child project and there is absolutely no other tutorial/documentation on this subject. Would you please provide a step-by-step example on how to set up automatic dependency management with Maven?
Hello @Mohammad Alavi welcome to the community :)
Are you facing issues with the child project not being able to fetch dependencies built by the parent project?
Also, the documentation that you have pointed out contains a section about automatic dependency management, what in that section didn't work for you?
According to the documents I expect the child build plan to be triggered when the parent builds successfully, but this does not happen.
This is my parent project POM file:
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>me.smash.bamboo</groupId>
<artifactId>parent-project</artifactId>
<version>1.0</version>
...
</project>
and this is my child project POM file which depends on the parent project:
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>me.smash.bamboo</groupId>
<artifactId>child-project</artifactId>
<version>1.0</version>
<dependencies>
<dependency>
<groupId>me.smash.bamboo</groupId>
<artifactId>parent-project</artifactId>
<version>1.0</version>
</dependency>
</dependencies>
...
</project>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the pom.xml!
Can you also share the "Maven Dependency Processor" task configuration and the plan dependencies configuration you have on your both parent and child plans?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I used maven dependency processor task with default configurations (all fields are empty) both in parent and child projects in the default stage's default job.
and the plan's dependency configuration for both child and parent projects is as follows:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
At first glance everything looks fine.
Giving a look at https://jira.atlassian.com/browse/BAM-18381, branches are not capable of triggering dependencies. Did you tried to trigger your child plans from the parent master?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.