This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Page tree
Skip to end of metadata
Go to start of metadata

Continuous Testing

We're running a Jenkins Continuous Integration (CI) server at http://builds.apache.org/.

Due to politics with Oracle, the project formerly known as Hudson was renamed Jenkins in early 2011. http://jenkins-ci.org/content/hudsons-future

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.

For more information, see http://wiki.apache.org/general/Jenkins which includes instructions for the PMC chair to grant access for a committer to get an administrative account.

The results can be viewed at the same links above for the jobs.

  • No labels