Workaround chrome-bot's special case wackiness.

archive_build.sh

 #!/bin/bash
 
 # Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # Script to archive build results.  Used by the buildbots.
 
 # Load common constants.  This should be the first executable line.
 # The path to common.sh should be relative to your script's location.
@@ skipping 40 matching lines @@
 # Parse command line
 FLAGS "$@" || exit 1
 eval set -- "${FLAGS_ARGV}"
 
 # Set if default from path is used
 DEFAULT_USED=
 
 # Reset "default" FLAGS_from based on passed-in board if not set on cmd-line
 if [ "$FLAGS_from" = "$DEFAULT_FROM" ]
 then
-  FLAGS_from="${IMAGES_DIR}/$FLAGS_board/$(ls -t1 \
-              $IMAGES_DIR/$FLAGS_board 2>&-| head -1)"
+  # Keep the directory name of the current image set (*.bin).
+  IMG_DIR="$(readlink ${IMAGES_DIR}/${FLAGS_board}/latest)"
+  FLAGS_from="${IMAGES_DIR}/${FLAGS_board}/${IMG_DIR}"
   DEFAULT_USED=1
 fi
 
 # Die on any errors.
 set -e
 
-if [ -z $DEFAULT_USED ] && [ $FLAGS_test_mod -eq $FLAGS_TRUE ]
+if [ -z $DEFAULT_USED ]
 then
-  echo "test_mod requires that the default from path be used."
-  echo "If non default behavior is desired, run mod_image_for_test manually"
-  echo "re-run archive build without test_mod"
-  exit 1
+  if [ $FLAGS_test_mod -eq $FLAGS_TRUE ] || \
+     [ $FLAGS_factory_install_mod -eq $FLAGS_TRUE ] || \
+     [ $FLAGS_factory_test_mod -eq $FLAGS_TRUE ]
+  then
+    echo "test_mod requires that the default from path be used."
+    echo "If non default behavior is desired, run mod_image_for_test manually"
+    echo "re-run archive build without test_mod"
+    exit 1
+  fi
 fi
 
 if [ ! -d "$FLAGS_from" ]
 then
    echo "$FLAGS_from does not exist.  Exiting..."
    exit 1
 fi
 
 if [ $FLAGS_official_build -eq $FLAGS_TRUE ]
 then
@@ skipping 60 matching lines @@
   popd
 fi
 
 if [ $FLAGS_factory_test_mod -eq $FLAGS_TRUE ]
 then
   echo "Modifying image for factory test"
   do_chroot_mod "${FLAGS_from}/chromiumos_factory_image.bin" \
       "--factory"
 fi
 
-if [ $FLAGS_factory_install_mod -eq $FLAGS_TRUE ]
-then
-  echo "Modifying image for factory install"
-  do_chroot_mod "${FLAGS_from}/chromiumos_factory_install_image.bin" \
-      "--factory_install"
-fi
-
 # Modify for recovery
 if [ $FLAGS_official_build -eq $FLAGS_TRUE ]
 then
-    BUILDVER=$(ls -t1 $IMAGES_DIR/$FLAGS_board 2>&-| head -1)
-    CHROOT_IMAGE_DIR=/home/$USER/trunk/src/build/images/$FLAGS_board/$BUILDVER
-   ./enter_chroot.sh -- ./mod_image_for_recovery.sh --board $FLAGS_board \
+  BUILDVER="$(readlink ${IMAGES_DIR}/${FLAGS_board}/latest)"
+  CHROOT_IMAGE_DIR=/home/$USER/trunk/src/build/images/$FLAGS_board/$BUILDVER
+  ./enter_chroot.sh -- ./mod_image_for_recovery.sh --board $FLAGS_board \
     --image $CHROOT_IMAGE_DIR/chromiumos_base_image.bin
 fi
 
 # Remove the developer build if test image is also built.
 if [ $FLAGS_test_mod -eq $FLAGS_TRUE ] ; then
   rm -f ${SRC_IMAGE}
 fi
 
+# Build differently sized shims. Currently only factory install shim is
+# supported, TODO(tgao): Add developer shim.
+if [ $FLAGS_factory_install_mod -eq $FLAGS_TRUE ]
+then
+  echo "Building factory install shim."
+  # HACK: The build system can't currently handle more than one image size
+  # at a time. Therefor eit's necessary to do another round of build after
+  # archiving the original build. This should be fixed in Chromite.
+
+  # HACK: cbuild has a special case when running on chrome-bot that
+  # zeroes out the current revision, which makes calling build_image directly
+  # fail. You must explictly call replace and specify a unique name numerically
+  # using build_attempt.
+  ./enter_chroot.sh -- ./build_image --board $FLAGS_board --factory_install \
+      --replace --build_attempt 7
+
+  # Get the install shim dir: It is the newest build.
+  # This is the output dir for the factory shim, the factory test and
+  # release images will remain in IMG_DIR, defined previously.
+  SHIM_DIR="$(readlink ${IMAGES_DIR}/${FLAGS_board}/latest)"
+
+  echo "Factory image dir: ${IMG_DIR}"
+  echo "Factory install shim dir: ${SHIM_DIR}"
+fi
+
 # Zip the build
 echo "Compressing and archiving build..."
 cd "$FLAGS_from"
 MANIFEST=`ls | grep -v factory`
 zip -r "${ZIPFILE}" ${MANIFEST}
 
 if [ $FLAGS_factory_test_mod -eq $FLAGS_TRUE ] || \
    [ $FLAGS_factory_install_mod -eq $FLAGS_TRUE ]
 then
-  FACTORY_MANIFEST=`ls | grep factory`
-  zip -r "${FACTORY_ZIPFILE}" ${FACTORY_MANIFEST}
+  # We need to have directory structure for factory package, as
+  # signing and packaging utilities need unpack_partitions.sh.
+  echo "Compressing factory software"
+  pushd ..
+  [ -n "${SHIM_DIR}" ] && rm -f factory_shim && ln -s "${SHIM_DIR}" factory_shim
+  [ -n "${IMG_DIR}" ] && rm -f factory_test && ln -s "${IMG_DIR}" factory_test
+
+  # Restore "latest" status to the original image.
+  # The "latest" symlink and latest timestamp are used extensively
+  # throughout the build scripts rather than explicitly specifying an image.
+  touch "${IMG_DIR}"
+  [ -n "${IMG_DIR}" ] && rm -f latest && ln -s "${IMG_DIR}" latest
+  FACTORY_MANIFEST=`find factory_shim factory_test -follow \
+      -type f  | grep -E "(factory_image|factory_install|partition)"`
+  zip "${FACTORY_ZIPFILE}" ${FACTORY_MANIFEST}
+  echo "Zipped"
+  popd
   chmod 644 "${FACTORY_ZIPFILE}"
 fi
 cd -
 
 # Update LATEST file
 echo "$LAST_CHANGE" > "${FLAGS_to}/LATEST"
 
 # Make sure files are readable
 chmod 644 "$ZIPFILE" "${FLAGS_to}/LATEST"
 chmod 755 "$OUTDIR"
@@ skipping 57 matching lines @@
 if [ $FLAGS_keep_max -gt 0 ]
 then
   echo "Deleting old builds (all but the newest ${FLAGS_keep_max})..."
   cd "$FLAGS_to"
   # +2 because line numbers start at 1 and need to skip LATEST file
   rm -rf `ls -t1 | tail --lines=+$(($FLAGS_keep_max + 2))`
   cd -
 fi
 
 echo "Done."