Well, we are a FreeBSD environment mostly so it is my familiar territory,
but I have no idea on how Jenkins works or where it lives.
Here's my crash course on Jenkins
You go to builds.apache.org
You login with your ASF LDAP credentials.
The PMC chair can add you to the admin group needed to access the build.
(instructions at http://wiki.apache.org/general/Hudson but Daryl, I
think you login into Minotaur/People and run
modify_appgroups.pl hudson-jobadmin --add=mmartinec
There are currently 3 builds: one for 3.3.x (solaris1 slave), one for
trunk (solaris1 slave) and one for trunk (freebsd slave).
The freebsd is a test slave.
https://builds.apache.org/job/SpamAssassin-trunk-FreeBSD/
If you go to
https://builds.apache.org/job/SpamAssassin-trunk-FreeBSD/53/consoleText
you can see the output. To me, it looks like we get a lot of spamd
errors and that perhaps something on the box is interfering with spamd
launching?
In the trunk, the script that runs on the freebsd slave is in
build/jenkins/run_build_freebsd
They dislike giving people shell but might be ok with giving out a shell
to try and figure out why it's not working. Eventually solaris1 zone
will be ramped down and we will have to use freebsd. So this is an
eventual thing to resolve.
I've updated http://wiki.apache.org/spamassassin/ContinuousTesting with
more of this information.
Regards,
KAM
