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

Bug 366336

Summary:	Unify Maven settings.xml across Hudson slaves
Product:	Community	Reporter:	Benjamin Bentmann <bentmann>
Component:	CI-Jenkins	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Benjamin Bentmann

2011-12-11 11:36:05 EST

From [0]:
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom

From [1]:
Downloading: http://maven.eclipse.org/nexus/content/groups/central/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom

Note that the two slaves use different servers to fetch dependencies. This doesn't make sense to me and appears to be a misconfiguration. Besides the OS, I would expect the slaves to behave the same with regard to downloads so I assume that either all should use maven.eclipse.org as a mirror or none of them (i.e. using the HTTP proxy).

I specifically observed this with the windows7tests and mac-tests slaves but other slaves might be affected as well. 

[0] https://hudson.eclipse.org/hudson/job/aether-core-nightly/jdk=Java%206%20R%2021%2064bit%20%28SUN%29,label=windows7tests/51/console
[1] https://hudson.eclipse.org/hudson/job/aether-core-nightly/jdk=Java%206%20R%2021%2064bit%20%28SUN%29,label=mac-tests/51/console

Comment 1 Benjamin Bentmann

2011-12-11 12:43:42 EST

If I may express a personal preference: After finding bug #365727 and seeing it being unresolved for almost a week now despite a relatively simple way of fixing it, I would rather not base CI builds on it by default.

Comment 2 Denis Roy

2011-12-12 13:23:12 EST

Do you know of a good way of making sure all the slaves have the same settings?  Relying on a file somewhere is error-prone.

Comment 3 Benjamin Bentmann

2011-12-12 17:33:33 EST

(In reply to comment #2)
> Do you know of a good way of making sure all the slaves have the same settings?
>  Relying on a file somewhere is error-prone.

Not really, sorry. Best thing I've seen so far was to manage the file centrally in source control, and have jobs on the slaves that would poll this location and check the contents out into the proper location.

Comment 4 Benjamin Bentmann

2012-03-10 10:37:20 EST

Ping.

Comment 5 Eclipse Webmaster

2012-03-12 11:23:13 EDT

All of the 'primary' slaves have a shared settings.xml file.  The Windows slave was updated to match some time ago, and I've just update the Mac slave(as the MAc and Windows boxes don't have access to the shared filesystem).

-M.

Comment 6 Benjamin Bentmann

2012-03-12 12:00:50 EDT

Thanks Matt, the Mac slave works fine now.