If you're using any of the Eclipse build or hudson servers, feel
free to employ the following tips to help your build finish faster.
->GETTING CODE: use the local filesystem to fetch
code. CVS is accessible via /cvsroot, SVN via /svnroot and git via
/gitroot. pserver and svnserve cannot compete with the local
filesystem in terms of performance and "robustness". The Git daemon
is very robust; however, using the filesystem cuts out the middle
man.
-> DOWNLOADING JARS: use download.eclipse.org. You won't
get a faster download.
-------> The downloads area is mounted in the local file system,
but you'll get better performance from http://download.eclipse.org
since it has massive caches.
-> WORKING AREA: Do not use your Committer home
directory as a working area. *build accounts (hudsonbuild,
wtpBuild, etc) have home directories on dedicated drives. These are
fastest, followed by /shared.
-> Temporary builds, even nightly ones, can be left (temporarily)
on the build server's /shared area for download by the core team.
You will get faster downloads from build.eclipse.org compared to
download.eclipse.org. As a reminder, /shared/technology is
accessible from http://build.eclipse.org/technology/, /shared/tools
is http://build.eclipse.org/tools/ and so on.
------> However, builds for the general public must be
promoted to download.eclipse.org and accessible via our
mirrors! See footnote [1] for more info.
-> CLEANING UP: Don't forget to clean up your
workspaces/working directories once in a while, since these areas
have limited disk space.
[1]
http://wiki.eclipse.org/IT_Infrastructure_Doc#See_which_mirror_sites_are_mirroring_my_files.3F
Denis
|