Here is my project structure:
It would be nice to use a modular plan in Bamboo. The parent poms are both aggregate and inheritable.
I would like to have the following stages in a plan:
Where I would have multiple plans, each compiling, testing and deploying individual projects from the overall project; i.e. dir2_2 under dir2 (dir being a substitute for a project name). In order to build dir2_2, I need to have the upper and core pom projects available.
Is this possible?
* Plan - Build All
* * Stage 1 - Build Proj 1
* * Stage 2 - Build Proj 2
Task a = Source Checkout task top-level upper parent POM to sub-dir .\
Task b = Source checkout task core POM to sub-dir .\dirN
Task c = Source checkout task project to sub-dir .\dirN\dirN_m
Task d = Call 'mvn deploy' inside .\dir\.dirN_m
"mvn deploy" will of course depend on tests passing, which of course will depend on a compile. Though it will be much easier to make dirN_m a self-contained project that doesn't require the ..\pom.xml and ..\..\pom.xml. You can release those POMs as artifacts to your Maven repo and list them as dependencies in dirN_m's pom.
N.B. Multiple checkout tasks is only possible in Bamboo 3.3. Another way to do that is to setup a "shell" project in your source repo that has the structure needed. You can accomplish that with svn:externals, git/hg sub-repos, P4 client specs, ClearCase viewspecs, etc...
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events