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

Why isn't my Ant task resolving ANT_HOME?

Dov Frankel March 15, 2019

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
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 18, 2019

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.

Dov Frankel March 20, 2019

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
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 20, 2019

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
AUG Leaders

Atlassian Community Events