Skip to main content
Jump to: navigation, search


Revision as of 08:48, 7 October 2010 by (Talk | contribs) (Accessing the Internet using Proxy)

General Information

The Eclipse Foundation runs a Hudson continuous integration server that eclipse hosted projects can take advantage of for their builds.  Currently this is hosted here:, but due to stability issues a new 'stable' instance has been created and is hosted here: . The Hudson server allows for the execution of Continuous Integration Builds, Nightly Builds, Integration Builds, Release Builds, and Testing. The 'stable' Hudson instance is maintained by the Eclipse Webmasters. The planned Hudson sandbox instance will be maintained by the eclipse community. Job creation will be limited to committers and admin rights are administered by the community as a whole.

Migrating to the 'new' Hudson service

If you have a build that is currently running on the 'unstable' Hudson instance(hosted on and you wish to move to the Hudson instance managed by the Foundation(hosted on you will need to file a bug against community->hudson with a subject like 'Move job job-name to'. Webmaster will then import the job and close the bug. Please note that the stable instance does not provide the same plugins as the unstable instance. You may also need to update your job configuration to account for differences in the Hudson deployment.

Hudson configuration and tools

Presently the 'new' hudson setup uses 3 SLES 11 x86_64 machines (1 master and 2 slaves), with bash as the default shell. These machines are behind a firewall so any outbound http(s) connections are proxied.

The following global variables are set(identically across installs):

  • JVM_OPTS: proxy data (see "Accessing the Internet" below)
  • ANT_ARGS: proxy data
  • ANT_OPTS: proxy data

Each node also has a .m2/settings.xml file with the proxy data.

Tools(and locations)

  • Maven 2.2.1 (installed automatically)
  • Maven 3.0 alpha 5 (installed automatically)
  • Maven 3.0-alpha-5-local (/shared/common/apache-maven-3.0-alpha-5)
  • Maven 3.0-alpha-6-local (/shared/common/apache-maven-3.0-alpha-6)
  • Maven 3.0-Beta-1 (/shared/common/apache-maven-3.0-beta-1)
  • Sun Java 5 SR 22 64bit (/shared/common/jdk-1.5.0-22.x86_64)
  • Sun Java 5 R 16 32bit (/shared/common/jdk-1.5.0_16)
  • Sun Java 5 R 22 64bit (/shared/common/jdk-1.5.0-22.x86_64)
  • Sun Java 6 R 21 32bit (/shared/common/sun-jdk1.6.0_21_i586)
  • Sun Java 6 R 21 64bit (/shared/common/sun-jdk1.6.0_21_x64)
  • Apache-ant-1.7.1 (/shared/common/apache-ant-1.7.1)
  • Apache-ant-1.7.0 (/shared/common/apache-ant-1.7.0)
  • Apache-ant-1.6.5 (/shared/common/apache-ant-1.6.5)
  • Headless Buckminster 3.6 (/shared/common/buckminster-3.6)
  • Buckminster 3.6 Integration (installed automatically)

Accessing the Internet using Proxy

Each Hudson instance has unrestricted access to the Internet by using The shell environment variables below are set for the hudson build user. If your build process overrides, or bypasses these variables, you must instruct your tools to use the proxy service to access external sites.

   JAVA_ARGS=" -Dhttp.proxyPort=9898 -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts=* -Dhttps.nonProxyHosts=* -Dftp.proxyPort=9898 -Dftp.nonProxyHosts=*"
   JVM_OPTS=" -Dhttp.proxyPort=9898 -Dhttps.proxyPort=9898 -DhttpnonProxyHosts=* -DhttpsnonProxyHosts=* -Dftp.proxyPort=9898 -DftpnonProxyHosts=*"
   ANT_ARGS=" -Dhttp.proxyPort=9898 -Dhttps.proxyPort=9898 -DhttpnonProxyHosts=* -DhttpsnonProxyHosts=* -Dftp.proxyPort=9898 -DftpnonProxyHosts=*"
   ANT_OPTS=" -Dhttp.proxyPort=9898 -Dhttps.proxyPort=9898 -DhttpnonProxyHosts=* -DhttpsnonProxyHosts=* -Dftp.proxyPort=9898 -DftpnonProxyHosts=*"

Additional Troubleshooting

From Martin Taal, via Forums:

Buckminster cvs materializing, uses a proxy, how is this configured?

To finish this thread. Michael Wenz pointed me to a change made in the cdo build (to solve this issue), a snippet from his email to me:

But I saw that the CDO build is green again and they still do an Ant call from Hudson that again triggers Buckminster. Previously that build failed with the same exception as ours did or do.

Not sure what these guys changed, but I saw that they added something in their build.xml that seems to fix this. I found 2 snippets that appear to be in connection with this: ... <condition property="no.proxy" value="${env.no_proxy}," else=""> <isset property="env.no_proxy" /> </condition> ...

... <java fork="true" jar="${@{app}.launcher}" dir="${@{app}.deploy.dir}" failonerror="true"> <env key="no_proxy" value="${no.proxy}" /> <properties /> <args /> </java> ...

Hudson for Committers

Hudson for Administrators

Duties of Administrators

  1. Hudson upgrades and restarts
  2. New Hudson accounts
  3. Add plugins
  4. Set policy for Hudson usage
  5. Watch changes to this wiki page
  6. Monitor the Hudson Inbox.

Who are the Adminstrators

  • Nick Boldt
  • Kim Moir
  • David Carver
  • Thomas Hallgren
  • Chris Aniszczyk

Please add other known administrators.

Hudson for Distributed Builds

  • Testing on Multiple Platforms
  • What is the Test-Slave Node?
  • How do I use the Test Slave Node to run Tests?

Copyright © Eclipse Foundation, Inc. All Rights Reserved.