Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Why does Bamboo run Java Specs with its own POM?

Alan Raison June 13, 2018

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!

1 answer

1 accepted

1 vote
Answer accepted
Gabriel Ribeiro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 14, 2018

Hi Alan,

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

thanks

Alan Raison June 15, 2018

Right. What is the benefit of this method? It seems like an arbitrary limitation (it won't improve security, for example) and an extra source of issues.

Like # people like this
Deleted user July 27, 2018

@Gabriel Ribeiro Just curious, if Bamboo doesn't use the pom.xml file from the bamboo-specs folder then why is it even required in the first place?

Like # people like this
Ivhani
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 12, 2021

I'm also curious. Why does bamboo use a default pom even in a case where there is a pom? 

It would make sense to use a default pom when there's none available, otherwise use provided pom.

@Gabriel Ribeiro what is the reasoning around using a default pom always?

Gabriel Ribeiro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 12, 2021

Hi @Ivhani and @[deleted] 

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.

-Dbamboo.repository.stored.specs.pom.sanitization.enabled=false
Like # people like this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events