The current build infrastructure is a mixture of dedicated machines and use of the LSF batch queue. This page attempts to describe the computers, operating systems, and infrastructure systems being used.

OSes and Packages

The currently supported operating systems for which the various RM packages are built are summarized in the following table.  The various packages currently supported by the Release Manager are listed across the top.  Currently supported operating systems are listed down the left.

OS ↓    \    Package →	Science Tools	Glast Release	CHS	TMineExt	GRB Analysis	Jenkins/LSF
redhat5-i686-32bit-gcc41						Jenkins
redhat5-x86_64-64bit-gcc41						LSF
Windows-i386-32bit-vc90						Jenkins
snowleopard-i386-32bit-gcc42						Jenkins
redhat6-x86_64-64bit-gcc44						LSF
mountainlion-x86_64-64bit-gcc44						Jenkins

= The build of this package on this OS is enabled in some form

= The build of this package on this OS is setup but not enabled

RM Control Node

The Release Manager is run off of fermilnx-v03.  This is where the lsfDaemon and the releaseManagerDaemon programs run which control the workflows for the RM system.

Build Machines

Many of the builds, including all of the builds using Jenkins, are being run on essentially dedicated build machines.  The various machines used by the different OSes are given in the following table, along with whether or not that OS's builds are running via Jenkins or LSF.

Packages, OSes, VersionTypes, and Variants (oh, my!)

While the table at the top of the page tells which OSes are enabled for which packages it doesn't tell the completely story.  Within each package/OS combination there are still a variety of version types (i.e. LATEST(Integration), HEAD(Release Candidate), and Release) and variants (Debug and Optimized) that may or may not be enabled and active for the specific package.  The following subsections give a breakdown by package and OS of the variants and version types that are available.   They all use the following key:

= This build configuration is enabled and automatically build when a new tag occurs

= This build configuration is enabled but does not automatically build when a new tag occurs

= This build configuration is not currently enabled in the database settings.