commit | c0c530cb7e2a44646fd3ff2d4950cc04c54e065c | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Fri Aug 30 13:08:25 2019 -0700 |
committer | chrome-bot <chrome-bot@chromium.org> | Mon Oct 21 15:12:08 2019 -0700 |
tree | bbdca2dd39d0f2564b11fc3219e1a6d6731238bc | |
parent | f3b30906543589ad0df8182bf25127c20252b439 [diff] |
termina_build_image: update x86 kernel comment We switched to using the bzImage directly rather than extracting the ELF image. Update the comment to match. BUG=None TEST=termina_build_image.py chromiumos_test_image.bin /tmp/termina Change-Id: Id77302909f3e7e335c4e80139138c4e4b9a8503b Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1779361 Tested-by: kokoro <noreply+kokoro@google.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org>
These are the guest packages for setting up a container to integrate with Chrome OS. This includes build scripts that are run in Google's internal continuous integration service.
The guest packages can be built with Bazel. The CrOS milestone to target and release name (stretch, buster, etc.) are required.
bazel build //... --action_env="MILESTONE=74" --action_env="RELEASE=buster" --host_force_python=py2
promote\_apt.sh MILESTONE
and promote\_container.sh MILESTONE
in scripts are used to promote containers from staging to live. NOTE: Whatever is the latest in staging is what gets promoted to live so make sure it's what was tested.