Ok, I thought I had this working, but it turns out I didn't. What I want to know is how do you share Maven artifacts between plans.
Here's my setup:
But - when I go to build project B, it doesn't do anything with that dependency. I was expecting it to download the projectA jar (for the appropriate branch), but there's nothing, so the build fails.
I can make it pass by making Project A do an 'install' instead of a 'verify' - but that only passes until the next time the ElasticBamboo restarts. Also, it doesn't work for branches - the install is a "last in wins" approach.
So here's the question:
* Is it possible to automatically share the maven-produced artifacts, without relying on the results of the install task?
* If so, what am I doing wrong with the above?
It turns out this feature does not exist - the online documentation is in a state of flux where some references to an old deprecated feature still exist.
To quote Marek Went:
Unfortunately, the Maven Dependency management never was meant to provide automatic dependency uploading/installing.
Maven Dependency management is meant for resolve automatic dependencies between plans.
So, it would not provide maven artifacts on your dependent build/job.
The only way to share Maven artefacts between plans is to:
This manual work around will quickly grow out of control if you are using several related Maven projects, and completely defeats the point of automating the plan dependency checks.
If you would like to see real dependency management in Bamboo, then please vote for https://jira.atlassian.com/browse/BAM-13881
I did find one thing wrong with the setup - the Maven Dependencies Processor needs to go onto Project A, as a final task, so that Project A knows which dependencies it produces.
Without that step (which I had in my real project, but not in the dummy example), ProjectB doesn't know that the artifact comes from ProjectA. Adding the step allows Bamboo to know the projects are related, and will make it so rebuilding ProjectA will build ProjectB
However, even with that step, ProjectB won't download the dependencies.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot