Locally, we use Hudson for the nightly builds.

Ptolemy and Kepler builds

The ptII nightly build is at

The kepler nightly build is at

Hudson has its own user database. Users can view the configuration for the builds (http://sisyphus:8079/hudson/job/ptII/configure).

To get an account, email Christopher

Updating Hudson

As root on sisyphus.

1. Probably a good idea to stop hudson first:

/etc/init.d/hudson stop

2. Run yum

yum --nogpgcheck update hudson

3. Restart

/etc/init.d/hudson stop

Install Hudson for RHEL 6.2

1. See

sudo wget -O /etc/yum.repos.d/hudson.repo
sudo yum check-update
sudo yum install hudson

2. Log in to sisyphus with ssh -X sisyphus, run firefox and, on sisyphus, go to http://localhost:8080

3. Hudson Plugins to add

  • Maven 2
  • Maven 3
  • Cobertura
  • Email-ext
  • FindBugs

4. Update /etc/sysconfig/hudson:


Note that HUDSON_HOME has to be set to /home/hudson to find our preexisting ptII and kepler jobs.

5. /etc/init.d/hudson was not terminating. I'm not sure what was up here, I ended up adding a & to the line that invokes java. I think the problem is that --daemon is not supported in Hudson3.0.

daemon --user "$HUDSON_USER" --pidfile "$HUDSON_PID_FILE" $JAVA_CMD $PARAMS > /dev/null


daemon --user "$HUDSON_USER" --pidfile "$HUDSON_PID_FILE" $JAVA_CMD $PARAMS & > /dev/null

Getting Hudson to run on port 80 under RHEL

Typically, Hudson appears on port 8080, but since we are testing web applications, we moved it to :8079 and set up apache on sisyphus to redirect to

See for Debian instructions. I'm running RHEL 5.8, so things were different.

The problem is that port 80 requires that applications run as root, which is a security issue for large Java applications. So I'm using an Apache server set up as a proxy.

Below are details about what we did:

1. Request that port 80 be opened up to sisyphus. We did this on and then "Update a Device"

2. Make sure that Apache is installed. We are running RHEL 5.8, so yum install httpd.x86_64

3. Edit /etc/httpd/conf/httpd.conf Important: Be sure to set allow only hosts, or else offsite visitors will use the machine as a proxy to access non-public library resources.

# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
<IfModule mod_proxy.c>
ProxyRequests On

<Proxy *>
Order deny,allow
Deny from all
Allow from

# Enable/disable the handling of HTTP/1.1 "Via:" headers.
# ("Full" adds the server version; "Block" removes all outgoing Via: headers)
# Set to one of: Off | On | Full | Block
ProxyVia On

# To enable a cache of proxied content, uncomment the following lines.
# See for more details.
<IfModule mod_disk_cache.c>
CacheEnable disk /
CacheRoot "/var/cache/mod_proxy"

# End of proxy directives.


<VirtualHost *>
DocumentRoot "/var/www/html"
ErrorLog logs/sisyphus-error_log
CustomLog logs/sisyphus-access_log common

ProxyPass /hudson

3. Configure Hudson to use port 8079. Edit /etc/sysconfig/hudson and update HUDSON_PORT="8079" and HUDSON_ARGS="--prefix=/hudson". Then run /etc/init.d/hudson shutdown and then /etc/init.d/hudson start and check

4. Open up port 80, 443 and 8079 on sisyphus. As root, I ran system-config-firewall, which worked in a terminal and opened up the ports. /sbin/iptables -L should include something like:

root@sisyphus ~]# /sbin/iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT icmp -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:http
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:https
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:8079
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target prot opt source destination
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[root@sisyphus ~]#

5. Start apache: /etc/init.d/httpd start should now work. If it does not, try

Also, try creating a dummy page for the webserver, httpd.conf has a line like

DocumentRoot "/var/www/html"

Create a index.html file at that location:


and then visit

If you are having firewall problems, try using wget on sisyphus to see if the page is up: wget should download a index.html file. If it does, but that URL is not visible outside of the machine, then either the machine firewall or the dept. firewall is blocking traffic.

6. Enable httpd after a reboot:

[root@sisyphus tmp]# /sbin/chkconfig httpd on
[root@sisyphus tmp]# /sbin/chkconfig --list httpd
httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@sisyphus tmp]#

Set up users for hudson

Install modules

  • Cobertura Plugin
  • SetEnv

ptII job

Build Trigger: 5 0 * * *

Set environment variables:


Other installations

Below are other packages that needed to be installed.

sudo yum install expat-devel.i686
sudo yum install expat-devel.x86_64

Running svn from the command line fails because Hudson uses Subversion 1.7

bash-4.1$ svn update
svn: The path '.' appears to be part of a Subversion 1.7 or greater
working copy. Please upgrade your Subversion client to use this
working copy.
bash-4.1$ which svn
bash-4.1$ svn --version
svn, version 1.6.11 (r934486)
compiled Apr 12 2012, 11:09:11

Copyright (C) 2000-2009 CollabNet.
Subversion is open source software, see
This product includes software developed by CollabNet (http://www.Collab.Net/).

The following repository access (RA) modules are available:

* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
- handles 'http' scheme
- handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
- with Cyrus SASL authentication
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme


The solution is to find a more recent version of Subversion for RHEL 6.2.

I ended up installing from Collabnet:

I had to create a link:

cd /usr/local/bin
ln -s /opt/CollabNet_Subversion/bin/* .

Email from Hudson is failing

On January 27, I added my email address to the hudson list

On January 30, hudson had this log message, but ptXX did not

Sending email for trigger: Still Unstable
Sending email to: ptXXX

On January 31, I started seeing messages like:

ERROR: Could not send email as a part of the post-build publishers.
^[[8mha:AAAAWB+LCAAAAAAAAABb85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWAAAAA=^[[0mjavax.mail.SendFailedException: Invalid Addresses;
nested exception is:
com.sun.mail.smtp.SMTPAddressFailedException: 554 <<>>... Relay operation rejected
nested exception is:
com.sun.mail.smtp.SMTPAddressFailedException: 554 <<cBRXXXX>>... Relay operation rejected