Sync to master head #3698
Merged
Sync to master head #3698
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…aging (second part) (#3251) 1) Radically change the structure of the repo. Now the root `pom.xml` file is not deployed to maven and is not a parent pom for any of the other modules, but is simply an aggregator pom, which aggregates other mostly independent of each other modules. 2) Update proto and grpc artifact to the latest generated versions as of time of this PR. 3) Add `cloudiot-v1` and `websecurityscanner-v1alpha` proto and grp artifacts (not released yet even in api-client-staging). Note, gapic clients for this apis are not added yet. 4) Rename `google-cloud-pom` parent artifact (for manual and gapic clients) to `google-cloud-clients`. 5) Move all manual and gapic clients from root directory to `google-cloud-clients` sub directory. 6) Make `google-cloud-bom` not a child of `google-cloud-clients` (former `google-cloud-pom`) anymore, keep it on root level so it becomes a sibling of `google-cloud-clients` (module which used to be its parent). 7) Similarly make `google-cloud-examples`, `google-cloud-testing` and `google-cloud-util` not children of `google-cloud-clients` and keep them on root level. Make these three modules also excluded from maven deployment (they will not be published to maven anymore). After this PR is done, additional work is required to fix circleci individual IT tests runs (should be trivial). Also deployment and documentation scripts must be modified accordingly (will be done right after pushing this PR).
Proto- and grpc- packages have moved to this repository. When we run integration on CI, we must build them, otherwise the tasks will fail from not being able to find dependencies.
We need to update the script since the clients moved.
- BigQuery Data Transfer - Cloud Redis
1) Add `utilities/stage_sites.py` (probably temporary solution). 2) Remove `utilities/create_site.sh` and `utilities/stage_release.sh` scripts. Other `.sh` releasing scripts will be removed soon. `RELEASING.md` was not update to reflect the changes. The readme will be updated after first successfull release with new structure (the only way to have an accurate releasing reame is to make the release first and record the steps). 3) Remove `.settings` folder. It is an eclipse-specific folder which hasn't been updated for 2 years. Nobody uses eclipse in our team, plus we should keep repo IDE-independent. 4) Move documentaiton look & feel files (.css, .html and .js files) to proper location (to `google-cloud-clients` from root). 5) Remove `google-cloud` maven dependency sample from landing page (since `google-cloud` metapackage was removed) 5) Several minor documentaiton-related fixes.
…3282) Also remove beta packages for dlp, as they are removed from googleapis. IoT packages were moved from `cloudiot` to just `iot`. Also regenerate clients with @BetaApi annotation for LRO-specific code.
…ture) (#3290) 1) Fix poms deployment config. 2) Fix documentaiton links in readmes. 3) Update main README (remove `goolge-cloud` metapackage reference). 4) Update `RELEASING.md` to reflect changes. The instructions try to avoid having mysterious scripts running in the release process and also ensures that all disruptive operations (actual release/push) are done explicitly and not somewhere in the middle of a mysterious script. 5) Remove `deploy.sh` and `finalize_release.sh` scripts. 6) Fix few previously broken links (bigquerydatatransfer and compute apidocs links)
PubSub: Update region tags to standard
Add the publisher error handler sample. As requested, the error handling part in the publishing quickstart sample is now removed.
[Storage] KMS integration
- add scopes
* Add presubmit test configs Add windows test config and add credentials for integration tests Invert the env var check Use fastconfigpush for faster keystore propagation Fix missing ;; in build script Allow LoggingAppender default options test to pass locally and on GCE Temporarily comment out the resource test Also grab surefire reports Fix java8-win bat path credentials path debug Set GCLOUD_PROJECT environment variable Add Java 11 test config try uploading surefire results as sponge_log.xml Fix BigTable IT args Temporarily test Java 11 Upload integration test output as sponge_log.xml too Revert "Temporarily comment out the resource test" This reverts commit f01bdbd. Revert "Allow LoggingAppender default options test to pass locally and on GCE" This reverts commit 90e28af. * Temporarily comment out the LoggingAppender default resource test. The default depends on the execution environment (GCE vs. locally) and Kokoro tests run on GCE. * Clean up debug output * Add continuous build configs * Fix the java10 build images to use Java 10, not 11
Fail fast when using utilities/batch_generate_apis.py if the local protoc version doesn't match the protobuf-java version defined in the pom.xml.
spanner: Add snippets for ReadContext
[Newer gRPC versions](https://github.com/grpc/grpc-java/releases/tag/v1.12.0) seem to check that we call this method. Currently shutdown waits for all messages to publish and return before shutting anything down, so awaitTermination likely won't do anything meaningful. In the future, we should make shutdown return promptly and use awaitTermination to wait for messages. I reported this at #3687. Fixes #3648.
This change also adds the jacoco coverage plugin in the spanner pom.xml and sets jacoco.skip to true to disable it by default. It can be enabled by passing -Djacoco.skip=false to the mvn command.
* Add Kokoro CI badge * Set integration test timeout at 10 minutes * Link to the devrel public bucket * Add java 8 on osx tests * empty commit to force ci
This will be used #3658 to add new callables that can't be autogenerated.
This replaces the raw calls to generate/check consistancy token with a polling wrapper that wait until all clusters are consistent.
|
@hzyi-google could you take a look? |
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
googlebot
added
the
cla: no
|
i deleted this branch.. |
|
Hello! Does this still need to be reviewed? Seems the PR is already merged. |
No. thanks !! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.