Continuous Builds
The LCGDM software development process is based on the idea of continuous builds. Whenever there is a change to the source code, in any of the components, a build system updates the installable packages in a shared directory. Anyone can install those packages, which represent the trunk release and the candidate release.
Our continuous integration process is built on Bamboo Bamboo
You can follow the build status using our Project Wallboard.
You can also have a look at https://svnweb.cern.ch/trac/lcgdm/wiki/Dpm/Dev/Recipes/BambooConfig for the detailed plan config of the components on bamboo.
What we build
Our builds are used both as nightlies, feeding our development cycle and as producers of releases for a well-known set of tags. For all the components that we manage we build:
- SVN trunk. This is expected to compile and be usable. The features can be incomplete or not yet completely tested.
- candidate release. A tag or branch is said to be part of the candidate release if the developer has marked it as such in SVN. This can be performed with a simple SVN command (see below). The candidate release build is expected to always compile and work. The features are expected to be reasonably complete and stable, and missing more deep testing, likely performed by external collaborators.
We build SVN trunk and release candidate for SL5 and SL6, hence populating and keeping up-to-date four repositories.