Greg will remove this line when he has reviewed this page {section: Overview } In addition to our nightly build and test we run a "continuous" build and test on a subset of platforms. The goal of these builds: *: Provide quick feedback if a commit breaks the builds or tests (without waiting until the next day to view the nightly results) *: Help spot race conditions in tests that fail sporadically, especially when subsequent runs of the test produce different results against the same code *: Eventually the desire is to run a build and test for each commit to Git. We don't currently have the CPU cycles available, largely because the tests take so long to run. {section: Current implementation} The continuous runs are submitted from =nmi-s006.cs.wisc.edu= in the =/home/cndrauto/continuous/= directory. To add a new continuous run: *: Login to =nmi-s006= and switch to the =cndrauto= user *: Copy the template directory from Git. It is in the =CONDOR_SRC/nmi_tools/continuous= directory. Put the directory into =/home/cndrauto/continuous/PLATFORM= where PLATFORM is the name of the platform you are testing against. It should match the NMI platform name, e.g. =x86_64_rhap_5= *: Replace "PLATFORM" in the files =run.sh= and =submit= *: Submit the Condor-Cron job: =condor_submit submit= {section: Modify a continuous run} *: Login to =nmi-s006= and switch to the =cndrauto= user *: Stop the appropriate job using =condor_rm=. You can run =condor_q | grep run.sh= to figure out which job to remove. *: Modify =run.sh= or =submit= as appropriate and then re-submit to condor: =condor_submit submit=