Here is a common scenario: You would like to do a build on some platform or set of platforms in order to ensure that you haven't broken the build process. What are your options? You could check in the code and wait for the nightly builds, but you may well break the build and receive fifty lashes with a wet noodle. A better solution is to *not* check in your code, but use NMI to build it on any platform that you like.
 
-Before you start, make sure that you have an account on submit-3.batlab.org.
+Before you start, make sure that you have an account on batlab.chtc.wisc.edu.
 
 From your usual machine,
 
 {code}
-  % ssh submit-3.batlab.org mkdir workspace
+  % ssh batlab.chtc.wisc.edu mkdir workspace
   % exit
   % cd to top of clone(CONDOR_SRC)
   % git write-tree
-  % git archive xxxxxx(hash created by git write-tree) | ssh submit-3.batlab.org cd workspace '&&' tar xf -
+  % git archive xxxxxx(hash created by git write-tree) | ssh batlab.chtc.wisc.edu cd workspace '&&' tar xf -
 For Windows execute below command,
-  % git archive xxxxxx(hash created by git write-tree) | ssh USERNAME@submit-3.batlab.org cd workspace ; tar xf -
+  % git archive xxxxxx(hash created by git write-tree) | ssh USERNAME@batlab.chtc.wisc.edu cd workspace ; tar xf -
 
 {endcode}
 
-Then, log into submit-3.batlab.org, and run the following commands
+Then, log into batlab.chtc.wisc.edu, and run the following commands
 
 {code}
   % cd workspace
@@ -46,7 +46,7 @@
 Some important options:
 
 *: =--without-tests= suppresses the automatic submission of tests when the build is done.
-*: =--platforms= takes a comma separated list of platforms. "all" is a good default. For a list of available platforms, see "Platforms" below.  You must specify the platforms you want.  (This is a change from the old BATLab.)  You can find a list of available platforms at http://submit-3.batlab.org/nmi/pool/status , look for "Pool usage by platform" in the left column. At the moment (2014-10-30) the set of platforms that we do nightly and rolling builds on is:
+*: =--platforms= takes a comma separated list of platforms. "all" is a good default. For a list of available platforms, see "Platforms" below.  You must specify the platforms you want.  (This is a change from the old BATLab.)  You can find a list of available platforms at http://batlab.chtc.wisc.edu/nmi/pool/status , look for "Pool usage by platform" in the left column. At the moment (2014-10-30) the set of platforms that we do nightly and rolling builds on is:
 *:: x86_64_Debian0,x86_64_Debian6,x86_64_Debian7,x86_64_Fedora19,x86_64_Fedora20,x86_64_MacOSX7,x86_64_MacOSX8,x86_64_RedHat5,x86_64_RedHat6,x86_64_RedHat7,x86_64_SL6,x86_64_Solaris11,x86_64_Ubuntu10,x86_64_Ubuntu12,x86_64_Ubuntu14,x86_64_Windows7,x86_64_Windows8,x86_RedHat5,x86_RedHat6,x86_SL5
 *: =--use-externals-cache= uses cached externals to speed the build. *May not work in new BATLab.* If you're testing a new external, do *not* use this option.
 *: =--release-only= builds the dynamic binaries, but doesn't package or return them. If you're just doing a compile test and don't need the binaries, this will speed the build by about 45 minutes. If you need to generate a package to give to a user (or to submit for testing), omit this option.
@@ -59,5 +59,5 @@
 
 {section: Checking your build's status}
 
-*:{link:http://submit-3.batlab.org/results/ HTCondor-specific status page} (Maintained by  at  (Maintained by Scot K. as of 2012-01).
-*:{link:http://submit-3.batlab.org/nmi/results/overview Metronome status page} (Maintained by Todd M. as of 2012-01.)
+*:{link:http://batlab.chtc.wisc.edu/results/ HTCondor-specific status page} (Maintained by  at  (Maintained by Scot K. as of 2012-01).
+*:{link:http://batlab.chtc.wisc.edu/nmi/results/overview Metronome status page} (Maintained by Todd M. as of 2012-01.)