Added --chrome_root option to sync_build_test.sh which, if specified, builds Chromium browser from source in the directory given.
Review URL: http://codereview.chromium.org/2824054
As with build_packages, only retries by default if you passed --jobs
even though build_image will indeed spuriously fail with only one job.
sync_build_test now uses jobs=#cores by default for both package and
image building. Eventually will also use this for gclient sync'ing
once that is better vetted.
Review URL: http://codereview.chromium.org/1564035
When grabbing buildbot image and test artifacts, properly install the test artifacts as if they were built by the user (with the user as owner).
Review URL: http://codereview.chromium.org/703001
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
Remove make_local_repo stage as it's not used by either build process.
Make portage build the default (--noportage still builds the old way).
Also add total time to build. A run of sync_build_test without args
on my machine takes 2:20min. Defaulting to --jobs=1 due to
instability reports.
Review URL: http://codereview.chromium.org/646015
Run a basic check on a buildbot grabbed image to make sure it has a
kernel installed in it.
Better failure recovery.
Review URL: http://codereview.chromium.org/553063
Here are some example ways to use the script (from comments)
sync_build_test.sh
syncs, recreates local repo and chroot, builds, and masters an
image in the checkout based on your current directory, or if you
are not in a checkout, based on the top level directory the script
is run from.
sync_build_test.sh --image_to_usb=/dev/sdb -i
same as above but then images USB device /dev/sdb with the image.
Also prompt the user in advance of the steps we'll take to make
sure they agrees.
sync_build_test.sh --top=~/foo --nosync --remote 192.168.1.2
builds and masters an image in ~/foo, and live updates the machine
at 192.168.1.2 with that image.
sync_build_test.sh --top=~/newdir --test "Pam BootPerfServer" \
--remote=192.168.1.2
creates a new checkout in ~/newdir, builds and masters an image
which is live updated to 192.168.1.2 and then runs
two tests (Pam and BootPerfServer) against that machine.
sync_build_test.sh --grab_buildbot=LATEST --test Pam --remote=192.168.1.2
grabs the latest build from the buildbot, properly modifies it,
reimages 192.168.1.2, and runs the given test on it.
Review URL: http://codereview.chromium.org/548094
