-
Notifications
You must be signed in to change notification settings - Fork 67
chore: introduce .kokoro templates for GraalVM jobs #3737
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
See the PR in sdk-platform-java for more context. TL;DR: we are introducing an additional Kokoro job to run native tests against GraalVM for JDK 17.0.9
See [sdk-platform-java#3737](googleapis/sdk-platform-java#3737) for more context. TL;DR: we are introducing an additional Kokoro job to run native tests against GraalVM for JDK 17.0.9
See [sdk-platform-java#3737](googleapis/sdk-platform-java#3737) for more context. TL;DR: we are introducing an additional Kokoro job to run native tests against GraalVM for JDK 17.0.9
See [sdk-platform-java#3737](googleapis/sdk-platform-java#3737) for more context. TL;DR: we are introducing an additional Kokoro job to run native tests against GraalVM for JDK 17.0.9
See [sdk-platform-java#3737](googleapis/sdk-platform-java#3737) for more context. TL;DR: we are introducing an additional Kokoro job to run native tests against GraalVM for JDK 17.0.9
See [sdk-platform-java#3737](googleapis/sdk-platform-java#3737) for more context. TL;DR: we are introducing an additional Kokoro job to run native tests against GraalVM for JDK 17.0.9
See [sdk-platform-java#3737](googleapis/sdk-platform-java#3737) for more context. TL;DR: we are introducing an additional Kokoro job to run native tests against GraalVM for JDK 17.0.9
See [sdk-platform-java#3737](googleapis/sdk-platform-java#3737) for more context. TL;DR: we are introducing an additional Kokoro job to run native tests against GraalVM for JDK 17.0.9
See [sdk-platform-java#3737](googleapis/sdk-platform-java#3737) for more context. TL;DR: we are introducing an additional Kokoro job to run native tests against GraalVM for JDK 17.0.9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what exactly does graalvm-a/b/c mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The full context is in a new support policy for GraalVM images. TLDR is that we want to keep a few placeholder jobs for frequently changing GraalVM images (e.g. we will now suport GraalVM for JDK 17 (C), 21 (A) and 23 (B)). In this way, we can avoid renaming the jobs based on the JDK versions these images run on.
hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/build.sh
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I give my LGTM but shall we stop naming the job as "-a", "-b", and "-c"? It's unclear what's being tested.
@@ -49,8 +49,9 @@ branchProtectionRules: | |||
- "Kokoro - Test: Integration" | |||
- "cla/google" | |||
- "OwlBot Post Processor" | |||
- "Kokoro - Test: Java GraalVM Native Image" | |||
- "Kokoro - Test: Java 17 GraalVM Native Image" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is unclear what is tested.
hermetic_build/library_generation/owlbot/templates/java_library/.kokoro/build.sh
Outdated
Show resolved
Hide resolved
|
|
# Configure the docker image for kokoro-trampoline. | ||
env_vars: { | ||
key: "TRAMPOLINE_IMAGE" | ||
value: "gcr.io/cloud-devrel-public-resources/graalvm_sdk_platform_b:3.45.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's change this according to the file name
Context: [we will introduce a new GraalVM job](https://docs.google.com/document/d/1bOeGtVFLsq5ts71If5pFXCvHIeNpbtBRvF6XQfavLZs/edit?tab=t.dcjxhf429j6t#bookmark=id.3s7d4dj247hr) and will leverage the hermetic build templates to propagate this change to some of the repositories. Each PR will be followed with ad-hoc changes such as sync-repo-settings (the cannot be templated). Demo PRs * googleapis/java-bigtable#2558 * googleapis/java-bigquerystorage#2937 * googleapis/java-storage#3029 * googleapis/java-datastore#1816 * There are manual changes in `build.sh`. We will add this file to the [ignored files in owlbot.py](https://github.com/googleapis/java-datastore/blob/8ceb62b5182e30b4f771d6c1b586a22fb084c9ac/owlbot.py#L48-L57) and will raise an issue to move this logic elsewhere (if feasible). * googleapis/java-firestore#2074 * googleapis/java-logging#1789 * googleapis/java-pubsub#2389 * googleapis/java-pubsublite#1839 * googleapis/java-spanner#3821
Context: we will introduce a new GraalVM job and will leverage the hermetic build templates to propagate this change to some of the repositories. Each PR will be followed with ad-hoc changes such as sync-repo-settings (the cannot be templated).
Demo PRs
build.sh
. We will add this file to the ignored files in owlbot.py and will raise an issue to move this logic elsewhere (if feasible).