-
Suggestion
-
Resolution: Answered
-
None
-
None
The automated Maven dependency management works great for detecting which plans are dependent on each other. This works very well.
However, this feature is next to useless when using multiple agents - especially the Elastic Bamboo agents. This is because when the triggered projects go to build, they can't find their dependencies.
As a manual work around, you can:
- publish the artefacts (build artifact and pom.xml) as Bamboo artefacts from the source project.
- download the artefacts in the destination project
- call 'mvn install:install-file' on the downloaded Maven artifacts so that they can be found during the build.
As a manual approach, this is very tedious, especially when setting up projects with several related dependencies.
All of this information is available to Bamboo, however, thanks to the Maven Dependencies Processor. That task needs a complement - a Maven Dependencies Artifact Downloader - which automates the steps described above.
(Note that this shouldn't require changes to the pom - unlike the deprecated Bamboo Artifact Sharing Maven Plugin)
[BAM-13881] Automated Maven Artifact Sharing
Just stumbled over this issue: We would really love to see this solved in one way or another. We have a project with a lot of individual modules with a separate live-cycle aka separate git repo & build.
But we still want to validate changes in the modules with "the whole thing" on a per feature branch level. Its way to tedious (and error prone and hard to automate etc) to implement the workaround above.
Thanks for the suggestion. We will keep it in mind for when we improve Maven integration in the future.
See http://twasink.net/2013/11/18/building-dependent-maven-projects-in-bamboo/ for a more in-depth description of the workaround mentioned above.
The answer was "thanks for the suggestion". The practical impact was "but we're not going to do it".
This was one reason I dropped Bamboo when Atlassian killed off the cloud version.