aboutsummaryrefslogtreecommitdiffhomepage
path: root/tools/interop_matrix
diff options
context:
space:
mode:
authorGravatar adelez <adelez@google.com>2018-08-07 13:57:46 -0700
committerGravatar GitHub <noreply@github.com>2018-08-07 13:57:46 -0700
commit6c3aa171f49e104356508eb3427b8671119cedfe (patch)
treeb965de41d1ddb661a8a1756b8f2ac099d85a9783 /tools/interop_matrix
parent67e8ddaf51a419e355ffd0243f6bf00299418c67 (diff)
parent3b1e34843b6470aa6845e8400b7b7d38f579f8a8 (diff)
Merge pull request #16274 from adelez/update_readme
Update README
Diffstat (limited to 'tools/interop_matrix')
-rw-r--r--tools/interop_matrix/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/interop_matrix/README.md b/tools/interop_matrix/README.md
index 40c02a1bc7..db84d9b454 100644
--- a/tools/interop_matrix/README.md
+++ b/tools/interop_matrix/README.md
@@ -9,7 +9,7 @@ from specific releases/tag, are used to test version compatiblity between gRPC r
We have continuous nightly test setup to test gRPC backward compatibility between old clients and latest server. When a gRPC developer creates a new gRPC release, s/he is also responsible to add the just-released gRPC client to the nightly test. The steps are:
- Add (or update) an entry in `./client_matrix.py` file to reference the github tag for the release.
- 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 --language cxx csharp python ruby php`
+ - `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`.