- Notifications
You must be signed in to change notification settings - Fork17
test: add all handwritten repos to downstream check#795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
generated-files-botbot commentedMar 20, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Warning: This pull request is touching the following templated files:
|
alicejli commentedMar 20, 2024
Failing java-spanner test, lint, and clirr checks in Java 8: |
burkedavison commentedMar 21, 2024
GraalVM 22.3.5 supports JDK 11 and 17, so the SDK has been compiled with JDK11 as its minimum. Thought: Can we disable compiling |
alicejli commentedMar 21, 2024
Should I just remove Java 8 from the matrix of tests? I think |
burkedavison commentedMar 21, 2024
Ah - in ci.yaml, we test Java 8 by compiling with JDK 17, and setting the SUREFIRE_JVM_OPT var to JDK 8. If we can compile with JDK17 in Spanner then test with JDK8, it should resolve the original issue. Is that possible? |
alicejli commentedMar 21, 2024
Just to double-check; this should be how we want to test for all the handwritten repos, not just Spanner right? And to check my understanding of what we want to test: the
Is that accurate? Or do we only need to test the compilation of the libraries in 17 and test with Java 8? |
burkedavison commentedMar 21, 2024
|
alicejli commentedMar 21, 2024
@suztomo Burke and I chatted about these tests and wanted to confirm that the |
suztomo commentedMar 21, 2024
Ensure Java 8 builds in the downstream repositories are checked. When a plugin stops working for Java 8, it should be caught in this repository, not after a release.
Ensure you use the same version of JDK that run the check in the downstream repository. E.g.,https://github.com/googleapis/java-bigtable/blob/79988b2295b8a6093fa0cd272d058299b1ce3a03/.github/workflows/ci.yaml#L119 Here is the protection rule defintion.
|
alicejli commentedMar 21, 2024
Yup that's the intention ofhttps://github.com/googleapis/java-shared-config/pull/795/files#diff-796de8db06964f64e6d050f294aa49f53a031b33a40a0e3a4bdedbb03a453fb1R45
Good catch.@suztomo Do you know why we picked Java 11 for |
Uh oh!
There was an error while loading.Please reload this page.
Fixes#790 ☕️
This adds all handwritten library repos to the downstream checks for clirr, lint, and test.
This removes the
javadoccheck in favor of just checking the javadoc generation with the doclet tool as that is the main documentation generation we care about.