You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have a project where the maven version I'd like to use for the build is part of the project's git repository. I'd like to define a Maven 3 executable to use the version in the checked-out repository (the one that is part of the build).
I tried to define an executable path as
${bamboo_build_working_directory}/env/thirdparty/apache-maven-3.5.2
and
${bamboo.build.working.directory}/env/thirdparty/apache-maven-3.5.2
But it doesn't seem that the executable is being found.
Is it possible to use Bamboo environment variables in defining an Executable?
No, using variables as Executable paths is not supported.
Using relative path:
env/thirdparty/apache-maven-3.5.2
seems to work for me though, so you might want to give it a shot.
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.