Community
Participate
Working Groups
Maven based builds and Athena based builds need the ability to access repos outside of eclipse.org. We went through this same issue when build2 was first brought online. P2 even will go through and try to download from other mirrors instead of always fetching from download.eclipse.org. This is causing issues currently with the WTP based builds unless all the artifacts are already there.
More info: Downloading: http://repo1.maven.org/maven2/org/sonatype/tycho/tycho-maven-plugin/0.8.0/tycho-maven-plugin-0.8.0.jar [WARNING] Unable to get artifact org.sonatype.tycho:tycho-maven-plugin:maven-plugin:0.8.0 from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out [ERROR] The build could not read 1 project -> [Help 1] [ERROR] The project org.eclipse.wst.xquery:org.eclipse.wst.xquery_parent:0.7.0-SNAPSHOT (/opt/public/jobs/cbi-wtp-inc-xquery/workspace/sourceediting/development/org.eclipse.wst.xquery.releng/pom.xml) has 1 error [ERROR] Unresolveable build extension: Plugin org.sonatype.tycho:tycho-maven-plugin:0.8.0 or one of its dependencies could not be resolved: Error transferring file: Connection timed out org.sonatype.tycho:tycho-maven-plugin:maven-plugin:0.8.0 from the specified remote repositories: central (http://repo1.maven.org/maven2, releases=true, snapshots=false) -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
The issue here seems to be this build isn't using our proxy. Does maven have it's own proxy settings? -M
(In reply to comment #2) > The issue here seems to be this build isn't using our proxy. Does maven have > it's own proxy settings? > > -M I can specify it to use a particular proxy port and server, if you let me know what it is. But on build2 and the original master this isn't necessary.
Build and Build2 are on a different network from the 'new' Hudson master. The proxy is: 206.191.52.34 port 9898. -M.
Okay, I think you need to create an appropriate entry in the ~/.m2/settings.xml file for the hudson user on each machine then to set the proxy port to be used. http://maven.apache.org/settings.html#Proxies I tried from the properties but that didn't seem to work.
I created the .m2/settings file and that seems to have done the trick. -M.
I don't think we can resolve this one just yet. There still are some issues. 1. Tycho 0.8 - 0.9 don't correctly resolve the proxy. There is a work around I need to tests. (One option is using tycho 0.10.0-SNAPSHOT) 2. There still appear to be some timeouts happening during the builds.
(In reply to comment #7) > I don't think we can resolve this one just yet. There still are some issues. > > 1. Tycho 0.8 - 0.9 don't correctly resolve the proxy. There is a work around I > need to tests. (One option is using tycho 0.10.0-SNAPSHOT) > > 2. There still appear to be some timeouts happening during the builds. Okay, now this can be resolved. In addition to the settings.xml, the following needed to be added to the JVM_OPTS: -Dhttp.proxyHost=206.191.52.34 -Dhttp.proxyPort=9898 If we could add those settings to the Hudson->Manage Hudson->Configure: GLOBAL Maven OPTS, that should take care of it for Maven 3 builds until tycho 0.10.0 is released.
I've updated the MAVEN_OPTS. Can you confirm that fixes the issue? -M.
The proxy settings also need to be added to the GLOBAL JVM_OPTS. Otherwise Ant based builds like Athena that need to access some items from the Internet can't download their dependencies. This will be critical for the Virgo project as well, since they use Ivy to download dependencies.
I've added the JVM_OPTS and ANT_OPTS global vars. Can you confirm that Ant is happy? -M.
(In reply to comment #11) > I've added the JVM_OPTS and ANT_OPTS global vars. Can you confirm that Ant is > happy? > > -M. No, I still had to add this manually to the Job's JVM Opts advanced setting for both Ant and Maven.
I note the Ant docs suggest setting ANT_ARGS (rather than ANT_OPTS) so I added the ANT_ARGS global and removed the proxy config from the Xquery build and it seems to have built fine. David can you confirm? -M.
Yes that seems to be working. Best way to test this in the forture is to click on the Workspace, and the select Wipe Workspace. This will clear all the cached artifacts, and force the system redownload everything. Otherwise you get a false positive that this is working.
