I've created some Java specs and tried uploading them but it seems that Bamboo tries to merge the specs project POM with one of its own; "bamboo-specs-generator". This caused me issues when declaring versions as properties, as properties weren't being merged into the new pom, but generally I wonder why bamboo is generating its own pom when my project has a perfectly good one already!
By default Bamboo Specs are executed with a default
pom.xml film, i.e. it will not use
pom.xml from your
bamboo-specs project. (from: Bamboo Specs troubleshooting)
You can find the default pom file at BAMBOO_INSTALL/atlassian-bamboo/WEB-INF/classes/bamboo-specs-pom.xml
Since the specs build will run inside the same environment as Bamboo, The POM gets sanitized by default to avoid less experienced users (or bad intentioned ones) to import dependencies that can potentially damage Bamboo.
You can disable this behavior (at your own risk) by adding the following property to <installation directory>/bin/setenv.sh and per Configuring your system properties documentations.
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