Getting Started

Katana can be set up mostly like a Buildbot instance, with a few differences. However, not all users trying to get started with Katana are familiar with Buildbot, so we will try to get you up and running with some simple examples.

Installing Pre-Requisites

Here, we assume you are starting with Ubuntu 14.04 as your host OS. If you are not, you will need to adjust accordingly, but use this as an example:

sudo apt-get update
sudo apt-get install build-essential
sudo apt-get install python-dev

wget http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11-py2.7.egg
sudo sh setuptools-0.6c11-py2.7.egg
sudo easy_install virtualenv
virtualenv --no-site-packages ~/buildbot-venv

source ~/buildbot-venv/bin/activate
pip install -Iv SQLAlchemy-migrate==0.7.2  # there are compatibility issues between versions
pip install -Iv SQLAlchemy==0.7.9
sudo apt-get install libmysqlclient-dev
pip install mysql-python
pip install buildbot  # running buildbot --version should display the version installed

# Install packages for running tests
sudo apt-get install libaprutil1
pip install mock
pip install sphinx  # generate docs
pip install pyflakes

Adjust System Settings

There are a few system settings that should be adjusted when you set up Katana:

Add the following to /etc/sysconfig.conf:

fs.inotify.max_user_watches = 524288
fs.inotify.max_user_instances = 512

We need to raise the default file handle limit per process from 1024 to 16000. Add the following to /etc/security/limits.conf:

*  soft  nofile 16000
*  hard  nofile 16000

Add the following to /etc/pam.d/common-session:

session required pam_limits.so

LDAP Support

If you want to use LDAP support with Katana, you probably want to install some related python packages:

#!/usr/bin/bash

sudo apt-get install libsasl2-dev 
sudo apt-get install libsasl2-dev libldap2-dev
pip install python-ldap

Installing Katana

Clone the git repository containing Katana. After doing this, from within your git clone, run:

pip install -e master
trial buildbot.test  # Runs the tests, look for errors

At this point, you should be ready to get started setting up configuration files. See the Configuration page for more information.