Description
Bamboo has undocumented restrictions with how you can use global variable substitution for a plan's goal. In our case, we have a batch of plans that all share the same set of verbose configuration options.
I defined a global variable, OPT.DBSETTINGS to represent a series of options that are common to several builds. This looks something like:
-Ddb.host=our.db.server -Ddb.port=5001 -Ddb.dbname=xe
It's a fair bit longer than that, but you get the idea. I passed this as a goal to our maven 1 builder like this:
Goal: ${bamboo.OPT.DBSETTINGS} full
This doesn't get passed to maven in the way I'd hoped. Instead of:
| Property | Value |
|---|---|
| db.host | our.db.server |
| db.port | 5001 |
| db.dbname | xe |
..maven receives:
| Property | Value |
|---|---|
| db.host | our.db.server -Ddb.port=5001 -Ddb.dbname=xe |
| db.port | not set |
| db.dbname | not set |
Other global variables of the form -Dpropertyname=value get through as expected.
Attachments
Issue Links
- is duplicated by
-
BAM-3251 maven builder errors if multiple goals are specified via a global variable.
-
- Closed
-
