Release 4.1.2-ondemand-rc3 does not work with our builds

[Andrew Paterson]

Came into work today to find out our Bamboo platform has been updated. Been trying to create and test new builds for our projects and it takes about 20 minutes to check SVN and it doesn't run the targets in our ant build scripts. The job just fails and doesn't create an artifact (jar file). It recognises the targets it needs to run but doesn't execute them. Not sure if this is an ANT issues. Currently we are using 1.7 but it looks like bamboo is using 1.8.

Anyone else having similar issues?

[Andrew Paterson]

I raised a ticket with your support team and they investigated and found out the problem related to what you said. Currently just running a build now.

[Przemek Bruski]

Is there anything interesting in the build log? Have you tried running the build locally against Ant 1.8?

[Andrew Paterson]

Please find attached a copy of the build log. It won't work locally due to way it accesses the projects in SVN

[Andrew Paterson]

these are two lines taken out of the log file where it seems to be failing:

command 16-Jul-2012 10:30:57 Beginning to execute external process for build 'Deployments - Test Console WAR - Common Jar'\n ... running command line: \n/opt/apache-ant-1.7.1/bin/ant\n -Djava.io.tmpdir=/tmp/HOSTPLAT-TCW-CCJ\n -f\n HOSTPLAT/trunk/com.compliantphones.common/build.xml\n clean\n jar\n ... in: /home/bamboo/bamboo-agent-home/xml-data/build-dir/HOSTPLAT-TCW-CCJ\n ... using extra environment variables: \nJAVA_HOME=/opt/jdk-6\nANT_HOME=/opt/apache-ant-1.7.1\nPATH=/opt/jdk-6/bin:/opt/bamboo-elastic-agent/bin:/opt/jdk-6/bin:/opt/maven-2.1/bin:/opt/maven-1.0.2/bin:/opt/ant-1.8/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/aws/bin:/opt/aws/amitools/ec2/bin:/opt/aws/apitools/ec2/bin:/home/bamboo/bin\n
simple 16-Jul-2012 10:30:57 Failing task since return code was -1 while expected 0

[Przemek Bruski]

You can fix this issue by changing the path to ant to /opt/apache-ant-1.8.2 in image capabilities.

Support is working on rolling out a global update for that, so you can also wait a bit and the problem should go away.