diff options
author | Adele Zhou <adelez@google.com> | 2018-08-07 11:38:53 -0700 |
---|---|---|
committer | Adele Zhou <adelez@google.com> | 2018-08-07 11:38:53 -0700 |
commit | 3b1e34843b6470aa6845e8400b7b7d38f579f8a8 (patch) | |
tree | 0432931a2025648c1ec96594d62428e16a452052 | |
parent | af1edd806ec5f4b7ad8c34a98515614be55d10c3 (diff) |
Update README
-rw-r--r-- | tools/interop_matrix/README.md | 2 |
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`. |