kokoro: Document command for publishing image

TEST=I ran it

Change-Id: Ib34e45f9d64561e318e4fbc78758d3a0dc191e87
Reviewed-on: https://chromium-review.googlesource.com/1422682
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: David Tolnay <dtolnay@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
This commit is contained in:
David Tolnay 2019-01-18 16:03:22 -08:00 committed by chrome-bot
parent db36427cd8
commit 284fcac560

View file

@ -42,6 +42,14 @@ If you have x20 access, move `crosvm-base.tar.xz` to `/teams/chromeos-vm/docker/
owner is `chromeos-vm-ci-read-write`. This owner is used to allow Kokoro to read the base image in
during the test run. The updated image will be used for future Kokoro runs until it is replaced.
```shell
prodaccess
cp crosvm-base.tar.xz /google/data/rw/teams/chromeos-vm/docker/
```
The cp command should preserve the right owner but to be sure you can confirm that it is
`chromeos-vm-ci-read-write` in the web ui: https://x20.corp.google.com/teams/chromeos-vm/docker
> **WARNING**:
> If the image tarball uploaded to x20 is defective in any way, Kokoro will fail to verify every
> crosvm change as if the change itself were defective. Please verify the image is good before
@ -69,4 +77,4 @@ docker container prune
docker rmi crosvm-base
```