Tools/BuildBot

Jenkins interface : http://buildbot.fusionforge.org/ (gives a list of different build queues)

Configuration of the builds (TODO: check me):

• box: miromesnil
• ssh port : 10022
• Contains a "VM" (openvz) which runs Jenkins :

# vzctl enter 204

In the VM :

• user albot
• /home/albot/.hudson
• /home/albot/.hudson/jobs contains the different job configurations
• for instance /home/albot/.hudson/jobs/fusionforge-Branch_5_1-build-and-test-deb/config.xml runs https://fusionforge.org/scm/viewvc.php/branches/Branch_5_1/tests/scripts/fusionforge-build-and-test-deb.sh?root=fusionforge&view=markup

We also use LXC, using a bridge setup with DHCP.

It's rather using standard Jenkins setup, with the pipeline plugin. There are :

• tasks to build lxc templates
• 3rd party software

It is meant to have the following build order:

unittest [if OK] -> deb src build -> [if OK] deb pkg build -> centos src build -> [if OK] rpm pkg build

• build in 'src' case: a 'source install' using install-ng
• build in 'pkg' case: a pkg build + a pkg install
• at the end of each build, Selenium tests are executed
• if the build is ok, the result is put in a repository

TODO/wish list:

• Automate task creation maybe using dsl plugin
  • improve the Jenkins plugin to pilot/setup Jenkins
  • put/visualize result in FRS
• Use master/slave Jenkins capability to enable parallel builds
• Try Buildbot as a Jenkins alternative

See also

• Virtual machine development environment: run the test suite in a complete preconfigured environment
• Test_Suite: what tests are run