Skip to content
gmarkall edited this page Apr 17, 2012 · 16 revisions

Work in progress

Buildbot master

The plan is for the buildbot master hardware to be installed in the week beginning 23/04/2012.

Build slaves

  • The buildbot master can also function as a build slave
  • CX1 - it is possible to set up a slave on CX1 that submits jobs using qsub.

Triggering the tests

At present a buildbot that has been used for testing is triggered by Github - Github posts a JSON payload describing each commit to a public-facing webpage that then records the payload and posts it to the buildbot web interface - this is done since it is not possible to expose the Buildbot's web admin port externally.

This setup is probably undesirable for the new buildbot because it creates security and potentially reliability issues. The Fluidity buildbot presently polls an email mailbox for messages the describe each commit - it is similarly possible to set Github to send emails to an email box that the new buildbot may poll in order to trigger builds

Proposed tests

This is a vague outline of the tests that could be run - in order to actually set these up as tests, we need to establish a list of commands that can be run to invoke each test, and to determine whether the test has passed or failed. The buildbot will determine if a test has passed or failed by examining the return code of each of the steps in the build process - if any of these are non-zero, the test will be considered to have failed. For example, in order to test the building of the most current revision of the OP2 sequential library and the C apps, we might expect to have a list of steps like:

git clone [email protected]:OP2/OP2-Common.git
cd OP2-Common/op2/c
./cmake.local
cd ../../apps/c
./cmake.local

There are a few environment variables that need to be set for most of the OP2 build processes - this is not a problem since we can specify exactly the values of the environment variables on a test-by-test basis.

  • Successful building of the OP2-Common sequential library in C and the fortran interface
  • Successful building of the apps
  • Successful building of the ROSE translator
  • Successful building of the
  • Checking the
Clone this wiki locally