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

Bug 326668

Summary:	windows7tests node cannot run maven build
Product:	Community	Reporter:	Stefan Dimov <stefan.dimov>
Component:	CI-Jenkins	Assignee:	Eclipse Webmaster <webmaster>
Status:	VERIFIED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	kaloyan
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
URL:	https://hudson.eclipse.org/hudson/job/cbi-wtp.inc-jpaeditor/
Whiteboard:

Description Stefan Dimov

2010-09-30 09:43:00 EDT

I'm a project lead of the WTP Incubator project - JPA Diagram Editor and today I've committed some minor changes and seems that the build fails with the error:

------------------------------------------
Started by user sdimov
Building remotely on windows7tests
[cbi-wtp.inc-jpaeditor] $ cvs -q -z3 update -PdC -D "Thursday, September 30, 2010 1:25:10 PM CUT"
cvs update: dying gasps from dev.eclipse.org unexpected
$ no changes detected
FATAL: Couldn't find any executable in /shared/common/apache-maven-3.0-beta-1
Recording test results
Archiving artifacts

You may check it here:

https://hudson.eclipse.org/hudson/job/cbi-wtp.inc-jpaeditor/

Comment 1 Kaloyan Raev

2010-09-30 10:15:29 EDT

I think I've found the reason. We don't restrict our Hudson Job to run on specific Hudson node. The failed builds are only when Hudson dispatches the build run on the windows7tests node. Now when I restricted the job to only the master node, the maven build starts successfully. 

It looks like the windows7tests node is not configured correctly to run maven builds.

Comment 2 Eclipse Webmaster

2010-09-30 10:21:52 EDT

The windows slave is only meant to run tests, not builds(hence the name).  I've re-configured hudson to only use the Windows box for tied jobs.

-M.

Comment 3 Stefan Dimov

2010-09-30 10:31:38 EDT

Seems the problem is solved ...