Difference between revisions of "Automatic Builds of GlueX Software"
From GlueXWiki
(add location of log files) |
(modify to use new sim-recon scheme) |
||
Line 2: | Line 2: | ||
* The builds are located in the directory /scratch/gluex/halld_builds on the JLab CUE. Everyday a new directory, named with the current date, is created in this directory, for example, /scratch/gluex/halld_builds/2010-02-28 . | * The builds are located in the directory /scratch/gluex/halld_builds on the JLab CUE. Everyday a new directory, named with the current date, is created in this directory, for example, /scratch/gluex/halld_builds/2010-02-28 . | ||
− | * Both the hdds | + | * Both the hdds and sim-recon packages are built. Latest versions of each are used. |
* The script run is /home/gluex/bin/nightly.sh. It is scheduled as a cron job for the [[GlueX shared account on the JLab CUE|"gluex" account]] on ifarml3.jlab.org. The job runs at 3:15 am daily. | * The script run is /home/gluex/bin/nightly.sh. It is scheduled as a cron job for the [[GlueX shared account on the JLab CUE|"gluex" account]] on ifarml3.jlab.org. The job runs at 3:15 am daily. | ||
* One cron job runs the builds on the various platforms, serially. The current platforms are: | * One cron job runs the builds on the various platforms, serially. The current platforms are: | ||
Line 10: | Line 10: | ||
* Both non-debug and debug builds are done on all platforms. | * Both non-debug and debug builds are done on all platforms. | ||
* Log files of the builds are created in the daily directory, for example, /scratch/gluex/halld_builds/2010-02-28/halld_jlabl3.log . For a particular platform, the output of both non-debug and debug builds are in a single log file. | * Log files of the builds are created in the daily directory, for example, /scratch/gluex/halld_builds/2010-02-28/halld_jlabl3.log . For a particular platform, the output of both non-debug and debug builds are in a single log file. | ||
− | * | + | * On Monday and Thursday mornings a summary of errors and warnings is sent to the halld-offline@jlab.org email list. The script to do this is /home/gluex/bin/nightly_report.sh and is run as a cron job (gluex, ifarml3). |
* To use one of the nightly builds, you can set up the environment as follows (assume you want to use October 3, 2010): | * To use one of the nightly builds, you can set up the environment as follows (assume you want to use October 3, 2010): | ||
− | setenv HDDS_HOME /scratch/gluex/halld_builds/2010-10-03/hdds | + | setenv HDDS_HOME /scratch/gluex/halld_builds/2010-10-03/hdds |
− | setenv HALLD_HOME /scratch/gluex/halld_builds/2010-10-03/ | + | setenv HALLD_HOME /scratch/gluex/halld_builds/2010-10-03/sim-recon |
source /group/halld/Software/scripts/build_scripts/gluex_env_jlab.csh | source /group/halld/Software/scripts/build_scripts/gluex_env_jlab.csh |
Revision as of 11:48, 17 March 2010
Every night a complete build of the source directory is done on several platforms at the lab.
- The builds are located in the directory /scratch/gluex/halld_builds on the JLab CUE. Everyday a new directory, named with the current date, is created in this directory, for example, /scratch/gluex/halld_builds/2010-02-28 .
- Both the hdds and sim-recon packages are built. Latest versions of each are used.
- The script run is /home/gluex/bin/nightly.sh. It is scheduled as a cron job for the "gluex" account on ifarml3.jlab.org. The job runs at 3:15 am daily.
- One cron job runs the builds on the various platforms, serially. The current platforms are:
- ifarml5.jlab.org (Fedora 8)
- jlabl3.jlab.org (RedHat Enterprise Linux 5)
- ifarml6.jlab.org (CentOS 5).
- Both non-debug and debug builds are done on all platforms.
- Log files of the builds are created in the daily directory, for example, /scratch/gluex/halld_builds/2010-02-28/halld_jlabl3.log . For a particular platform, the output of both non-debug and debug builds are in a single log file.
- On Monday and Thursday mornings a summary of errors and warnings is sent to the halld-offline@jlab.org email list. The script to do this is /home/gluex/bin/nightly_report.sh and is run as a cron job (gluex, ifarml3).
- To use one of the nightly builds, you can set up the environment as follows (assume you want to use October 3, 2010):
setenv HDDS_HOME /scratch/gluex/halld_builds/2010-10-03/hdds setenv HALLD_HOME /scratch/gluex/halld_builds/2010-10-03/sim-recon source /group/halld/Software/scripts/build_scripts/gluex_env_jlab.csh