diff options
| author |  Adele Zhou <adelez@google.com> | 2017-11-15 16:42:12 -0800 |
|---|---|---|
| committer | Adele Zhou <adelez@google.com> | 2017-11-22 11:10:10 -0800 |
| commit | e4d63e644630987ceaa098540d012026e290f610 (patch) | |
| tree | d651ecfc564088566ca464f461727df0bb1db5cb /tools/interop_matrix/README.md | |
| parent | 935aa47e6574c3506c520122eaea23b541edc46a (diff) | |
Give a command example with multiple languages.
Diffstat (limited to 'tools/interop_matrix/README.md')
| -rw-r--r-- | tools/interop_matrix/README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tools/interop_matrix/README.md b/tools/interop_matrix/README.md index 588afe4fd4..40c02a1bc7 100644 --- a/tools/interop_matrix/README.md +++ b/tools/interop_matrix/README.md @@ -8,8 +8,8 @@ from specific releases/tag, are used to test version compatiblity between gRPC r ## Step-by-step instructions for adding a GCR image for a new release for compatibility test 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 java release `v1.9.9`, do - - `tools/interop_matrix/create_matrix_images.py --git_checkout --release=v1.9.9 --language=java` +- 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` - 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`. |