Ugh, it worked on my machine because of my .ssh/config but need to
explicitly specify port for it to work on buildbot.
TBR=sosa
BUG=5532
TEST=This change was in the previous location of cbuilbot.py and working
correctly.
Change-Id: Id53a76bcb5d43c37ac725267864048d833f5a6ee
Review URL: http://codereview.chromium.org/3144005
TEST=Ran locally outside of chroot. Required change to remove Exception OSError as
e because "as" is a Python 2.6'ism
Review URL: http://codereview.chromium.org/3146001
Adds arm_extra_bootargs to boot.desc and to cros_make_image_bootable.
TEST=tegra2 dev-board build_packages, build_image --fast worked
BUG=broken tree
Change-Id: Ifdfeda66f1eb5e5b1e618706eeba269f31fa9913
Review URL: http://codereview.chromium.org/3069031
Breaks make_image_bootable out of build_image into a separate
script. In addition, it make a helper .sh in the OUTPUT_DIR
to let make_image_bootable be re-run on an image with the same
arguments that were passed in via build_image.
This change also removes the use of the boot/ directory in
OUTPUT_DIR.
TEST=build_image verified; image_to_usb --test_image; booted l13
build_image; image_to_vm; qemu booted
build_image verified; image_to_usb; booted l13
BUG=chromium-os:5081
Review URL: http://codereview.chromium.org/3066037
Change-Id: I627d678089aa71c353347f387ad5b14063fd4e7b
BUG=none
TEST=use this script with a (correct) password that includes punctuation such as one of these: $&+,/:;=?@
Review URL: http://codereview.chromium.org/3058046
Modifying gsdcurl to accept username and password from the environment. Switching cros_download_latest_image to use gsdcurl
Merge branch 'master' of ssh://chromiumos-git/crosutils
Switching back to MixedCase. Wrong style guide...
Switching to match external style guide.
Dropping unneeded arg as per review.
Fixing copyright.
Making the prompts go to stderr. Renaming for tab completion.
Adding gsdcurl utility for pulling for Google Storage for Developers.
BUG=None
TEST=None
Review URL: http://codereview.chromium.org/3060043
This conforms to the new layout of scripts in which all scripts
other than make_chroot and enter_chroot are installed in the
chroot using an ebuild.
Review URL: http://codereview.chromium.org/3084012
I'd be OK just setting the defaults in the original command as well.
BUG=4246
TEST=ran it and image booted in normal mode.
Review URL: http://codereview.chromium.org/3008021
This is a first pass. I'll review this code myself and do more
testing, but I wanted to get folks a look at it to make sure I
was going in the right direction.
BUG=none
TEST=ran using both cell and hostname scenarios
Review URL: http://codereview.chromium.org/3007002
Clean up command-line argument used to disable re-download of image bits down to the upgrade server. This is now handed via a much more concise "--no_copy_archive" argument. and user output output "fast restart" messages
Output information on how to run the "image_to_live.sh" client unconditionally (even if a client isn't being launched by this instance).
BUG=none
TEST=Reran commands, observed output
Review URL: http://codereview.chromium.org/2919009
cros_copy_upgrade_server had a bug where it would always start servers
on port 8081 regrdless of whether that port was free. This was a bug
in the "get next free port" code.
BUG=chromium-os:4776
TEST=Reran multiple instances at once, run netstat -nlt
Review URL: http://codereview.chromium.org/2975006
Currently the output of build_image signs the kernel partition with the recovery keys on the final image. This script allows us to replace the kernel vblock and resign the kernel with the right set of keys (for example, using the normal boot path kernel keys, or the keys for factory install, etc.)
BUG=4623
TEST=Tested by running the script on one of the latest builbot images (801) and resigning with test kernel keys. The resulting image was dd-ed off to an SSD and was succesfully able to boot on one of our dev systems with our custom firmware with both dev mode and recovery mode turned off.
To test (can do outside chroot):
1) Download the latest image from the buildbot (I used build 801)
2) Run script with the following arguments and paths adjusted below
resign_image
--from /path/to/chromiumos_image.bin \
--datakey /path/to/vboot_reference/tests/devkeys/kernel_data_key.vbprivk \
--keyblock /path/to/vboot_reference/tests/devkeys/kernel.keyblock \
--vsubkey /path/to/vboot_reference/tests/devkeys/kernel_subkey.vbpubk \
--vbutil_dir /path/to/vbutil/binaries
--to image.out
This re-signs the image with the normal test keys (instead of recovery as done by build_image)
3) Copy the image to an SSD drive
dd if=image.out of=/dev/ssd [replace with the correct device]
4) Boot with the latest custom firmware in normal mode (recovery and dev mode turned off).
5) Profit!
Review URL: http://codereview.chromium.org/2938004
