This article suggests that Bamboo global and build specific variables can be referred to in build scripts or maven.
https://confluence.atlassian.com/bamboo/passing-bamboo-variables-to-a-build-script-289277351.html
While the example works, it appears that if I define my own bamboo variable either globally or at the plan level, they are not replaced.
I suspect that "built in" variables are substituted, but user defined global or plan variables are not.
If in my maven task, I set the goal to
clean test -Dvms.database.user=${vms.db.user} -Dvms.database.password=${bamboo.buildNumber}
Then I can clearly see that the built in bamboo.buildNumber is replaced, where as my global variable vms.db.user is not (as shown below).
clean test -Dvms.database.user=${vms.db.user} -Dvms.database.password=1
Hey John,
You can certainly Bamboo plan and Global variables in-line in a Script task or in your Maven goal. It just needs the bamboo prefix.
If your plan / global variable is vms.db.user you can reference in a Script task with this syntax: ${bamboo.vms.db.user}
Hope this helps. :)
Awesome. Glad to hear it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.