anybox.buildbot.openerp 0.4.3

Buildbot slave software

For slave software itself, just follow the official buildbot way of doing:

virtualenv buildslaveenv
buildslaveenv/bin/pip install buildbot-slave
bin/buildslave create-slave --help

System build dependencies

The slave host system must have all build dependencies for the available buildouts to run. Indeed, the required python eggs may have to be installed from pypi, and this can trigger some compilations. In turn, these usually require build utilities (gcc, make, etc), libraries and headers.

There is a package for debian-based system that installs them all.

PostgreSQL requirements

You must of course provide a working PostgreSQL installation (cluster).

The default configuration assumes a standard PostgreSQL cluster on the same system as the slave, with a PostgreSQL user having the same name as the POSIX user running the slave, having database creation rights.

You can provide host, port, and password (see slaves.cfg file to see how to express in the master configuration).

WARNING: currently, setting user/password is not supported. Only Unix-socket domains will work (see below).

The default blank value for host on Debian-based distributions will make the slave connect to the PostgreSQL cluster through a Unix-domain socket, ie, the user name is the same as the POSIX user running the slave. Default PostgreSQL configurations allow such connections without a password (ident authentication method in pg_hba.conf).

To use ident authentication on secondary or custom compiled clusters:

• set the value of pg_host to the value of unix_socket_directory seen in postgresql.conf or leave it blank if missing or commented. The psql executable and the client libraries use the same defaults as the server.

• you must provide the port number if not the default 5432, because the port identifies the cluster uniquely, even for Unix-domain sockets

For custom compiled installations, you must also provide the path to the binaries and libraries directories in the pg_bin and pg_lib optional properties.

Examples:

# Default cluster of a secondary PostgreSQL from Debian & Ubuntu
pg_port = 5433

# Compiled PostgreSQL with --prefix=/opt/postgresql,
# port set to 5434 and unix_socket_directory unset in postgresql.conf
pg_bin = /opt/postgresql/bin
pg_lib = /opt/postgresql/lib
pg_port = 5434

# If unix_socket_directory is set to /opt/postgresql/run, add this:
pg_host = /opt/postgresql/run

Registration

Have your slave registered to the master admin, specifying your version of PostgreSQL (e.g, 8.4, 9.0). The best is to provide a slaves.cfg fragment (see slaves.cfg.sample for syntax).

If you happen to have several available versions of PostgreSQL on the same host, then make one slave for each one.

Tweaks, optimization and traps

• eggs and openerp downloads are shared on a per-slave basis. A lock system prevents concurrency in buildout runs.

• Windows slaves are currently unsupported : some steps use ‘/’ separators in arguments.

• Do not start the slave while its virtualenv is “activated”; also take care that the bin/ directory of the virtualenv must not be on the POSIX user default PATH. Many build steps are not designed for that, and would miss some dependencies. This is notably the case for the buildout step.

0.4.3

• Documentation improvements

0.4.2

• Documentation improvements

0.4.1

• Initial release on pypi