LSST Logo

Automated Builds

What does it mean?

The Waterfall display (screenshot at right) is a timeline of build activity. In general,  green  indicates success, and  red  failure. The column headers indicate whether each column's latest build succeeded or failed. For example, in the screenshot at the right, the first four columns' most recent tasks have succeeded, and the last two columns' have failed.

The waterfall's current columns, from left to right (last updated 2/23/2009):

name OS arch command description dependencies schedule
1. Triggered Trunk CentOS 64-bit scons opt=3 install declare Test each trunk package against its dependencies minimal After every check-in to a package's trunk (plus an 11-minute settling time)
2. 32-bit
3. 64-bit current
4. Nightly Trunk 64-bit minimal Nightly, 3 am (Central Time)
5. 32-bit
6. 64-bit current
7. Nightly Release Pipeline 64-bit newinstall.sh

lsstpkg install LSSTPipe		 Release packages, installed from scratch Nightly, 12:30 am (Central Time)
8. 32-bit
9. Incremental Release Pipeline 64-bit Update release packages installed by 7. and 8. (without starting from scratch) On demand (not scheduled)
10. 32-bit

Terms

OS
Currently the nightly build only runs CentOS, although we will add Mac OS, since it is a supported platform.
arch
LSST supports both 64- and 32-bit architectures. As long as developers use 32-bit machines (netbooks, for example) we will probably continue to test the build on them.
dependencies
We test trunk packages against both their "minimal" and "current" dependencies, to cover a reasonable compatibility range. Testing against every version in between would be prohibitive.
minimal
Build against the minimum versions that a package declares in its ups/<package_name>.table file. For example, if a package lists setupRequired(daf_base >= 3.2.1), then we'll build it against daf_base version 3.2.1, even if the "current" version is newer.
current
Simple enough: use the current versions of a package's dependencies, as listed in current.list.