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,460,397
Community Members
 
Community Events
176
Community Groups

Why isn't my Ant task resolving ANT_HOME?

Edited

I'm trying to use Ant along with Ivy, and am trying to use Ant to do a user-install of ivy. This command works locally (and on the default Ubuntu elastic bamboo image when run as a Script task):

ant -f ${ANT_HOME}/fetch.xml -Ddest=user ivy

But when I try using the Ant build task configured like so:

ant-config.png

I keep getting this error in my logs:

Buildfile: ${ANT_HOME}/fetch.xml does not exist!

But I see in the blue log box for the Ant task that ANT_HOME is defined:

ant-logs.png

I've verified that the fetch.xml file does exist in /opt/apache-ant-1.10.5, so what am I doing wrong?

1 answer

1 accepted

1 vote
Answer accepted

Hi @Dov Frankel

Usually, the task body does not resolve variables from the terminal. The variable ANT_HOME does not exist in the Bamboo application variable context. You should be able to find a variable called bamboo_capability_system_builder_ant_<name> where <name>is the label you gave to your ANT capability when creating it. You can find the right variable in your build logs.

Your test works on a script task because the variable you add there is evaluated on the terminal and therefore the variable is available.

Please let me know if that makes sense to you.

Thanks! I was able to use:

${bamboo.capability.system.builder.ant.Ant 1.10}/fetch.xml

 It took a little tinkering to get the naming right, but that worked.

Like Daniel Santos likes this

You are welcome!
I'm glad to see that you can now move forward.

Like Dov Frankel likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events