*:::: (You can also use "=scp nmi-s006:/space/tmp/release-$RELEASE/public/v$RELEASE_MAJOR/'*' ./=" to copy the binaries over. rsync provides the advantage that you can re-run it over and over again if your transfer is interrupted and you won't re-copy what you already have.)
*::: Option 3: Derek has a script to search through a given NMI rundir and move everything we need. The script lives in the nmi_tools directory in git, and is called =move_to_afs=. Beware that this script will eat up around 8 gigabytes while it runs. It's also old and crusty and should be avoided.
-1: Pre-release source tarball. The source tarball is created every night as part of the nightly builds. Nick's =nmi-extract-results= script will extract it along will all of the binary tarballs. Otherwise, you can extract it yourself. If you look in the =rundir= of a given NMI runid, you should see a tarball in =userdir/common= named =results.tar.gz=, which contains the source tarball. Extract it like so:
-{code}
-tar zxvf results.tar.gz condor-X.Y.Z.tar.gz
-{endcode}
+1: Pre-release source tarball. The source tarball used to be created every night as part of the nightly builds. After the conversion to cmake, it is no longer created. While releasing 7.5.5, I created it by hand by tarring the contents of =userdir/common= in the =rundir= of the NMI build. I put these files in a top-level directory named =condor-X.Y.Z= and I removed the =soar= directory. Nick's =nmi-extract-results= script will also create the source tarball.
The source should be placed in =/p/condor/public/binaries/vX.Y/X.Y.Z= using the name "=condor_src-X.Y.Z-all-all.tar.gz=".
