I am new to bamboo and currently struggling how to achieve the following whilst adhering to best practices (no workarounds or nasty tricks).
My git repository:
|- Project A
|- Project B
|- Project C
I currently have:
- 1 single repository (Technology).
- 1 Project (Technology)
|- Plan for A
|- Plan for B
|- Plan for C
When pushing a change to Project A, all plans trigger.
When pushing a change to Project A, only plan A triggers.
Create multiple linked repositories (one per project and use subdirectory expression). If you have 40 projects then you should do this 40 times.
How does the competition do it?
I come from different tool background where you simply install a maven/ivy plugin and the tool would 'modularise' the projects and build only the modules that have changed (2 min).
As long as new modules contain the module descriptor (pom or ivy) then new module would be picked up automatically. Is there anything similar in this case?
How can I build only changed modules rather than every single plan?
Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...
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