This solves this issue where if we don't upload to gsutil and instead
just archive locally we still have the test tarball.
BUG=chromium-os:16014
TEST=Ran with no gsutil option set and a tarball file.
Change-Id: I5e14801f7b0a58f589a400278274fb566e580bea
Reviewed-on: http://gerrit.chromium.org/gerrit/1921
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
to the output of images uploaded to Google Storage. This is a stop gap solution
until I migrate all builders to uploading with the new structure.
BUG=NA
TEST=Ran on a finished buildbot to ensure the proper behaviour
Review URL: http://codereview.chromium.org/6749018
from within the chroot.
It also fixes a number of style issues.
It changes the meaning of cros_workon "list-all" to list all available
packages, and adds "list-live" to list all live packages.
It changes things that load chromeos-common.sh from the installer to
load it from /usr/lib/installer.
BUG=chromium-os:4230
TEST=synced, rebuilt chroot, made packages, made images, built chrome
from source, and wrote an image to a USB stick.
Review URL: http://codereview.chromium.org/6240018
Change-Id: I90c34420af1a64020402bafef8e9e77f56837c02
Change-Id: Id4ed6af96e0b621f4ad36966fad45c887b991373
BUG=None
TEST=Ran a fresh build_packages and build_image for x86-generic.
Review URL: http://codereview.chromium.org/5689004
archive_build.sh has code to archive host prebuilts, but the code isn't working because of a typo in archive_build.sh.
The typo: $FLAGS_board is misspelled as $FLAGS_BOARD.
BUG=chromium-os:10148
TEST=Ran prebuilt.py with --sync-host option
Change-Id: I50129b1fdfb931b1c076a064b970d7d943f556ac
Review URL: http://codereview.chromium.org/5724001
is abused throughout the script and this is where end up at when prebuilt
is called
BUG=8389
TEST=Ran from the directory archive_build actually runs from.
Review URL: http://codereview.chromium.org/4119017
Enabled host prebuilt upload on the x86-generic target.
BUG=NA
TEST=Tested on an x86-generic build to ensure it uploads as expected
Review URL: http://codereview.chromium.org/4128014
BUG=4547
TEST="untestable - the failure can only occur on chrome-bot, which I don't have access to "
Change-Id: Ia90eaa7c673f16533dbc397adf7f76e6404c6d2b
Review URL: http://codereview.chromium.org/3978005
BUG=None
TEST=None
TBR=djmm
Merge branch 'master' of ssh://chromiumos-git/crosutils
Fixing command line to work with file acls.
Merge branch 'gsd'
Merge branch 'master' into gsd
Fixing typo in command line.
Refactoring gsutil archiving into a function. Adding optional gsd_generate_index step.
Adding ACL option to archive_build.sh
Review URL: http://codereview.chromium.org/2803030
TEST=From an already built image dir, ran archive_build with --notest_mod
set and verified the image had chromiumos_base_image.bin and chromiumos_image.bin.
Review URL: http://codereview.chromium.org/2111015
TEST=Tested with building a new image, looking in the output directory, running
the image and running vi.
Review URL: http://codereview.chromium.org/2075019
BUG=1970
TEST=Running archive build with clean build and producing
a test image and normal image and zip file. Also running
with custom from and getting an error code with test_mod=true
This change is required because mod_image_for_test requires it
to be inside chroot. Since the buildbot is the main user
of this script, this deals with that use case. Other users
of this script will have to run mod_image_for_test manually
outside of archive_build
Review URL: http://codereview.chromium.org/2008001
sync_build_test runs build_autotest that way.
archive_build bzips up the autotest artifacts.
run_remote_tests can run autotest artifacts from a prepackaged directory. Note that because build_platform is in a different repository than these other files, it's unfortunately forced to be reviewed separately in http://codereview.chromium.org/661197 and committed independently.
Review URL: http://codereview.chromium.org/660189