Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 311860

Summary: Error: java.io.IOException: java.io.IOException: ant: not found
Product: Community Reporter: Martin Taal <mtaal>
Component: CI-JenkinsAssignee: CI Admin Inbox <ci.admin-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: d_a_carver
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Martin Taal CLA 2010-05-06 07:42:01 EDT
I am getting the following exception (see below) when doing a build on Hudson. I did not change anything in the build environment. When I try to solve this by selecting a specific ant version I get the exception: 'Unpack facility not configured'. This eventhough I set the property:
org.eclipse.update.jarprocessor.pack200=/shared/common/ibm-java2-ppc-50/jre/bin

and I pass this option to the director:
<jvmarg value="-Dorg.eclipse.update.jarprocessor.pack200=${org.eclipse.update.jarprocessor.pack200}" />


Started by user mtaal
ln -s 2010-05-06_07-37-52 /opt/users/hudsonbuild/.hudson/jobs/emf-teneo-nightly/builds/185 failed: -1
Building remotely on build2
[org.eclipse.emf.teneo] $ cvs -q -z3 update -PdC -D "Thursday, May 6, 2010 11:37:52 AM UTC"
? releng/org.eclipse.emf.teneo.releng.buckminster/${tools}
$ no changes detected
[org.eclipse.emf.teneo.releng.buckminster] $ ant -file build.xml -DSITE_PACK200=true -DBUILD_TARGET=build.and.test -DTENEO_UPDATE_SITE_TYPE=interim -DCLEAN_TOOLS=false -DVERSION=1.2.0 -DBUILDTYPE=N -DBUCKMINSTER_LOGLEVEL=DEBUG -DSITE_SIGNING=true -Dorg.eclipse.update.jarprocessor.pack200=/shared/common/ibm-java2-ppc-50/jre/bin build.and.test
FATAL: command execution failed.Maybe you need to configure the job to choose one of your Ant installations?
java.io.IOException: java.io.IOException: ant: not found
	at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
	at java.lang.ProcessImpl.start(ProcessImpl.java:65)
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
	at hudson.Proc$LocalProc.<init>(Proc.java:149)
	at hudson.Proc$LocalProc.<init>(Proc.java:121)
	at hudson.Launcher$LocalLauncher.launch(Launcher.java:633)
	at hudson.Launcher$ProcStarter.start(Launcher.java:268)
	at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:778)
	at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:754)
	at hudson.remoting.UserRequest.perform(UserRequest.java:114)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:270)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
	at java.lang.Thread.run(Thread.java:595)
Archiving artifacts
Recording test results
Emma: looking for coverage reports in the provided path: build/result/test/output/hibernate-coverageReport.xml
Sending e-mails to: mtaal@elver.org
Finished: FAILURE
Comment 1 David Carver CLA 2010-05-06 09:35:37 EDT
In your job config, make sure you have the job tied to the Master node for now.  Going forward we will need to be careful about specifying hardcoded paths for the jvms, as slave machines will have different locations and different jvms.
Comment 2 Martin Taal CLA 2010-05-06 11:36:59 EDT
Thanks this solves this part, I am now stuck with 305675 though... But that's another story.

gr. Martin