[Spamassassin Wiki] Update of "ContinuousTesting" by KevinMcGrail

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The "ContinuousTesting" page has been changed by KevinMcGrail:
http://wiki.apache.org/spamassassin/ContinuousTesting?action=diff&rev1=14&rev2=15

Comment:
More clarification on Jenkins jobs, how they run and how to admin them.

  
  Therefore, the Jenkins/Hudson server for the SA Project has a bit of an identity crisis.  This is evident in documentation, server names, existing scripts, etc.  But the Jenkins CI server will run build/hudson/run_build (3.3 branch) or build/jenkins/run_build (trunk) to test the latest code after every check-in to SVN.
  
+ 
  As of May 2011, there are jobs for both the 3.3 branch and trunk:
  
  [[https://builds.apache.org/job/SpamAssassin-3.3.x/]]
  [[https://builds.apache.org/job/SpamAssassin-trunk/]]
+ 
+ Both of these jobs run on the solaris1 slave and use the script in trunk under build/jenkins/run_build
+ 
+ There is also a test job we are using to prepare for the eventual replacement of the solaris1 zone for Jenkins.  
+ 
+ [[https://builds.apache.org/job/SpamAssassin-trunk-FreeBSD/]]
+ 
+ This job runs on a freebsd slave and use the script in build/jenkins/run_build_freebsd
+ 
+ 
+ To login at [[http://builds.apache.org/]], use your ASF LDAP credentials.
  
  To administer the jobs, you must be a member of hudson-jobadmin group.