1: Pre-release binary tarballs to the web.
The binaries are not available to the public until they've been pushed to the mirrors (see step 14). However, they still need to be placed into AFS for the download system to find. If the version of Condor is =X.Y.Z=, then place the binary releases of Condor for the various available architectures into =/p/condor/public/binaries/vX.Y/X.Y.Z= Note that for any particular architecture, =unstripped= binaries should not be released to the web if there is a corresponding =condordebugsyms= tarball.
*:: UNIX: Mostly this involves copying everything off of nmi-s006 and into /p/condor/public/binaries/...
-*::: Option 1: Use Nick's shiny "nmi-extract-results" script, which lives in tools/nmi-interaction. It's also in ~nleroy/bin on nmi-s006.
+
+*::: Option 1: Use nmi_crowbar
+1:::: Log onto chopin, as it's got a giant /scratch.1 and we'll need the space.
+1:::: Pull down the binaries: =nmi_crowbar --runid=193173 --download --flatten --unpack-style=release --scratch=/scratch.1/adesmet --into=/scratch.1/adesmet/7.4.0-binaries=
+1:::: Delete the checksum files, we don't currently use them =rm *.md5 *.sha1=
+1:::: Delete debug files is debugsym are present for that platform
+
+*::: Option 2: Use Nick's shiny "nmi-extract-results" script, which lives in tools/nmi-interaction. It's also in ~nleroy/bin on nmi-s006.
{linebreak}
The script writes to ./cache and ./public -- and will create these directories if they don't already exist. The cache is to maintain a list of things that it's already extracted from, so if you run it again, it won't do unnessesary work.
{linebreak}
@@ -211,7 +218,7 @@
$ rsync -av --rsh=ssh * nation:/p/condor/public/binaries/v7.1/7.1.4
{endcode}
-*::: Option 2: Do it by hand:
+*::: Option 3: Do it by hand:
*:::: for a given build's GID, run the following on nmi-s006:
{code}
GID=cndrauto_nmi-s006.cs.wisc.edu_1167884128_28240
