Last updated January 17, 2013.
Adding a new testbot is described below.
Yes, this seems complicated by comparison with a simple module. This is the simplest we've been able to make it.
There is a screencast: https://vimeo.com/40406036 (It refers to the former home of this page, but the information should be familiar.)
- Install Debian Squeeze 64bit with swap, probably 512MB of swap. We've been using 5 GB and 8GB of disk. The device can be anywhere that can *reach* qa.drupal.org. (Amazon EC2 AMI ami-e00df089 works; Debian AMIs are here; EBS-backed ones are best.)
- Give your machine a permanent name ending in -mysql in /etc/hosts and /etc/hostname (my-machine-mysql). Use the primary interface IP address for the hostname in /etc/hosts. If you're building with ganeti, just *start* with a name like "drupaltestbotxxx-mysql.osuosl.test and you'll avoid this pain.
- Set the hostname:
hostname $(cat /etc/hostname)
apt-get update && apt-get upgrade
aptitude install sudo php-pear puppet
- Edit /etc/puppet/puppet.conf to add
pluginsync=trueto the [main] section.
puppetd --server testbotmaster.devdrupal.org --test
- Add any keys you need to ~/.ssh/authorized_keys. A standard set of keys is already provided in authorized_keys2 by puppet
- Load the provided default database:
gzip -dc /tmp/drupaltestbot.sql.gz | mysql drupaltestbot
- If you want PIFR to be the git repo (probably), then(as in "git checkout 6.x-2.10")
rm -rf project_issue_file_review
git clone git://git.drupal.org/project/project_issue_file_review.git --branch 6.x-2.x
git checkout <tag>
- Visit the site and log in as admin/drupaltesting1
- Visit admin/pifr/configuration and configure the client - enter the key you got from qa.drupal.org, and set the concurrency.
- You can run tests of any branch, tag, or patch locally (on the testbot itself) using the form at admin/pifr/run-test
- Request enabling the testbot on qa.drupal.org and verify that it completes testing.