aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorGravatar Jan Tattermusch <jtattermusch@google.com>2019-01-09 16:44:43 +0100
committerGravatar Jan Tattermusch <jtattermusch@google.com>2019-01-09 21:16:44 +0100
commitbd5e15608d217e7a5efcaac73dc45f7d1be28a21 (patch)
tree008c4fd5caf2c7fbecad1f134569ee31da4ff2d1
parent4f11b9650099212b9bb3c01b6b73e977a20c2c8e (diff)
minor doc updates
-rw-r--r--tools/interop_matrix/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/tools/interop_matrix/README.md b/tools/interop_matrix/README.md
index 531bef82b8..5a8965757e 100644
--- a/tools/interop_matrix/README.md
+++ b/tools/interop_matrix/README.md
@@ -11,8 +11,8 @@ We have continuous nightly test setup to test gRPC backward compatibility betwee
- Build new client docker image(s). For example, for C and wrapper languages release `v1.9.9`, do
- `tools/interop_matrix/create_matrix_images.py --git_checkout --release=v1.9.9 --upload_images --language cxx csharp python ruby php`
- Verify that the new docker image was built successfully and uploaded to GCR. For example,
- - `gcloud beta container images list --repository gcr.io/grpc-testing` shows image repos.
- - `gcloud beta container images list-tags gcr.io/grpc-testing/grpc_interop_java_oracle8` should show an image entry with tag `v1.9.9`.
+ - `gcloud container images list --repository gcr.io/grpc-testing` lists available images.
+ - `gcloud container images list-tags gcr.io/grpc-testing/grpc_interop_java_oracle8` should show an image entry with tag `v1.9.9`.
- Verify the just-created docker client image would pass backward compatibility test (it should). For example,
- `gcloud docker -- pull gcr.io/grpc-testing/grpc_interop_java_oracle8:v1.9.9` followed by
- `docker_image=gcr.io/grpc-testing/grpc_interop_java_oracle8:v1.9.9 tools/interop_matrix/testcases/java__master`