ci: testing old GraalVM version

suztomo · suztomo · commit 168cc886dd15 · 2022-03-29T13:44:33.000-04:00
diff --git a/.github/sync-repo-settings.yaml b/.github/sync-repo-settings.yaml
@@ -58,6 +58,7 @@ branchProtectionRules:
     - "build (11, java-bigquery, test)"
     - "build (11, java-bigquery, lint)"
     - "build (11, java-bigquery, clirr)"
+    - "graalvm (11, java-orgpolicy)"
     - "cla/google"
 - pattern: java7
   # Can admins overwrite branch protection.
diff --git a/.github/workflows/downstream-maven-plugins.yaml b/.github/workflows/downstream-maven-plugins.yaml
@@ -57,9 +57,9 @@ jobs:
         # When a new version of native-maven-plugin fails to run in a downstream
         # library, it's likely to be an incompatibility with GraalVM version.
         # In that case, you need to upgrade the Docker container used in the
-        # tests in the downstream repositories. Example PR:
-        # https://github.com/googleapis/testing-infra-docker/pull/195
-        graalvm-version: 22.0.0.2
+        # tests in the downstream repositories (not just this field below).
+        # Example: https://github.com/googleapis/testing-infra-docker/pull/195
+        graalvm-version: 21.2.0
         native-image: true
     - run: java -version
     - run: sudo apt-get update -y
