chore: migrate java-shared-config to monorepo#13481
Conversation
* deps: update actions/github-script action to v7 * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md --------- Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
…rtifact (#755) * chore: merge doclet test with rest of client-library-checks * add back in separate test * update script and permissions * update script * update permissions * update permissions * update permissions * rename file * update permissions * update script * replace cd with pushd and popd
…rtifact (#759) * chore: fix storage downstream check to use sdk-platform-java-config artifact
This check is now running in the stage job and is no longer needed in Github.
…-plugin to v3.6.3 (#706)
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
* chore: updating contribution guideline b/323263307 * exclude CONTRIBUTING.md from templates
🤖 I have created a release *beep* *boop* --- ### Updating meta-information for bleeding-edge SNAPSHOT release. --- This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
…771) * fix: update DocFX profile with properties * test: see if these changes are needed
…-info-reports-plugin to v3.5.0 (#763)
…r-plugin to v3.12.1 (#760)
* deps: update actions/github-script action to v7 * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md --------- Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
…lugin to v3.5.0 (#775)
* deps: update actions/setup-java action to v4 * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md --------- Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
…, and Cloud Build
01eac5a to
84bc89c
Compare
…es from root reactor
17e3f10 to
7501606
Compare
…ory to avoid compiling GAX under Java 8
79cfbc0 to
77df590
Compare
…cloud-core-bom during downstream builds
ec1b0ad to
236b59e
Compare
…cks and workflows
|
Existing places (e.g. sdk-platform-java-config/pom.xml) that point to released version of java-shared-config in this repo need to be updated to use relative path now. |
There was a problem hiding this comment.
Do you mind sharing how the downstream tests work now? I guess we test the downstream libraries in this repo with the changes in this PR?
There was a problem hiding this comment.
Thanks for the question. Yes, the downstream checks verify that the proposed changes to java-shared-config in the PR do not break dependency convergence or packaging for the main client libraries in the monorepo.
- Local Installation: The workflow first compiles and installs the modified local version of
google-cloud-shared-configfrom the PR branch into the runner's local Maven cache (~/.m2/repository) using.kokoro/build.sh. - Mocking Downstream Usage: The .kokoro/client-library-check.sh script is invoked. Since this script was migrated from the standalone repo, it currently:
- Clones
google-cloud-javaat the latest stable tagged release. - Rewrites the parent pom reference in
sdk-platform-java-configin the cloned repo to point to the localgoogle-cloud-shared-configversion we just built in Step 1.
- Clones
- Validation: It then runs
dependencies.sh(to run the upper-bound dependency convergence check) and theflatten-plugin-check(to verify flattened POM dependency resolution) on the target client libraries (like BigQuery, Spanner, Storage) using the newly modified configuration.
There may be some optimizations possible to improve this test in the future, but for now, most of the existing testing logic has been re-used.
1431d4a to
93a9dbf
Compare
…est discovery, and restore logback Kokoro configs
ec1d6d1 to
d08aed0
Compare
|
|



b/519273974