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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,466,618
Community Members
 
Community Events
176
Community Groups

User defined global and plan variables are not replaced in maven task goal.

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 

1 answer

1 accepted

1 vote
Answer accepted
Jeremy Owen Atlassian Team Feb 28, 2018

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. :)

 

<facepalm> why didn't I think of that.

Thanks Jeremy. Rookie mistake.  It most certainly works.

Jeremy Owen Atlassian Team Mar 01, 2018

Awesome. Glad to hear it.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events