Cruisecontrol RPM builds

The creation of RPM packages from source tarball is done with the central build system called cruisecontrol.testbed. Access to this machine is restricted to users of the CTB testbed.

The build system runs a Cruisecontrol instance that monitors several spec file directories of the old VL-e project. The sources for this setup rarely need to be touched, only the files

centos5-i386-projects-mwsec 
centos5-x86_64-projects-mwsec

are relevant as they contain the base component lists for the packages to be build. Cruisecontrol monitors the SPEC file directory

span.nikhef.nl:/srv/project/rpmbuild/SPECS-MWSEC/

to see if any file is touched; this will trigger a new build of the corresponding component. This directory is automatically kept up-to-date (from within cruisecontrol itself) by tracking the SVN repository at

https://ndpfsvn.nikhef.nl/repos/mwsec/packaging/fedora/trunk

Note: the build cycle of Cruisecontrol is set to 5 minutes, so it may take up to 5 minutes to update the spec file, and another 5 minutes from there to trigger the actual build. To monitor the status of Cruisecontrol at http://cruisecontrol.testbed:8080/ or http://cruisecontrol.testbed:8080/dashboard/dashboard you may need to tune the network access parameters of your browser; here is an example in Firefox:

network.proxy.no_proxies_on localhost, 127.0.0.1
network.proxy.socks 127.0.0.1
network.proxy.socks_port 8888
network.proxy.socks_remote_dns true
network.proxy.socks_version 5
network.proxy.type 1

This should be combined with a SOCKS proxy to a testbed machine, e.g.:

ssh -n -N -f -D 8888 span.nikhef.nl