You can set an environment variable called ANT_HOME to point to your other version.
I know this works if you set this in the shell that runs TeamCity, however that only let's you point to a single other version (which is fine for my needs).
However, I've not tried setting ANT_HOME in the environment variables section of the build configuration which should allow you to specify a different version for each build configuration.
1) What about custom ant scritps IN THE SAME FOLDER of the same ant home dir? e.g.: /opt/ant/bin/ant <---- standard ant for command line use /opt/ant/bin/TCant <---- custom ant for TeamCity /opt/ant/bin/ccand <--- custom ant for Cruise Control
Build configuration settings has just an "Ant home path" textfield... and this is not useful for this purpose (I need to specify a certain ANT SCRIPT, not a PATH)
2) What is the deal with buildAgent.properties ??? OK, I can setup environment variabless this way:
env.MIVAR=whatever literal
but I need to define (into the buildAgent.properties) environment variables based on others previous environment variables... (some hardcoded in bash_profile, for instance). How do the agent parse theese variables?? What if I put something like this (in the buildAgent.properties file)
You can set an environment variable called ANT_HOME to point to your other version.
>
I know this works if you set this in the shell that runs TeamCity, however that only let's you point to a single other version (which is fine for my needs).
>
However, I've not tried setting ANT_HOME in the environment variables section of the build configuration which should allow you to specify a different version for each build configuration.
You can set an environment variable called ANT_HOME to point to your other version.
I know this works if you set this in the shell that runs TeamCity, however that only let's you point to a single other version (which is fine for my needs).
However, I've not tried setting ANT_HOME in the environment variables section of the build configuration which should allow you to specify a different version for each build configuration.
Paul
I have important questions
1) What about custom ant scritps IN THE SAME FOLDER of the same ant home
dir?
e.g.:
/opt/ant/bin/ant <---- standard ant for command line use
/opt/ant/bin/TCant <---- custom ant for TeamCity
/opt/ant/bin/ccand <--- custom ant for Cruise Control
Build configuration settings has just an "Ant home path" textfield... and
this is not useful for this purpose (I need to specify a certain ANT SCRIPT,
not a PATH)
2) What is the deal with buildAgent.properties ??? OK, I can setup
environment variabless this way:
env.MIVAR=whatever literal
but I need to define (into the buildAgent.properties) environment variables
based on others previous environment variables... (some hardcoded in
bash_profile, for instance).
How do the agent parse theese variables?? What if I put something like this
(in the buildAgent.properties file)
env.MIVAR=$ ?
env.MIFANCYVAR=%MIVAR% ?
env.MIOLDFASHIONEDVAR=env.MIVAR ?
I need to know all the syntax rules for the buildAgent.properties file... in
order to get it useful and... operative.
3) Can I make use indistinctly of $ or %var% in a unix agent
propierties file?
what about the server? what about the build configuration config pane?
Some kind of documentation about theese rules whould be very valuable for
me.
Thanks in advance
Regards
Gaston Martin
Buenos Aires - Argentina (I'm not native english spoken, excuse my faults)
"Paul Brooks" <no_reply@jetbrains.com> wrote in message
news:29678914.1155114180524.JavaMail.itn@is.intellij.net...
>
>
>