Repository navigation
[sdk-platform-java] Graalvm tests are failing because Cloud Build triggers are not migrated #12724
Description
See tests errors in java-bigtable that graalvm images were not released as part of the sdk-platform-java release.
RuntimeError: Failed to pull image gcr.io/cloud-devrel-public-resources/graalvm_sdk_platform_a:3.59.0.
This is because the Cloud Build triggers are not updated to point to google-cloud-java after monorepo migration.
Metadata
Metadata
Assignees
Labels
No labels
Activity
suztomo commentedon Apr 9, 2026
I manually added 3.59.0 Docker tag for this time.
suztomo commentedon Apr 15, 2026
For those who work on this. Check the condition of the Cloud Build trigger with regard to Git tag pattern.
In sdk-platform-java repository, https://github.com/googleapis/sdk-platform-java/blob/main/.github/workflows/create_additional_release_tag.yaml was responsible to create additional tags.
chingor13 commentedon Apr 15, 2026
This workflow was migrated, but the migration script added a path filter which doesn't apply to release events.
build: create additional tags on release (#12811)
chingor13 commentedon Apr 15, 2026
The create_additional_release_tag ran with workflow_dispatch: https://github.com/googleapis/google-cloud-java/actions/runs/24481550464
chingor13 commentedon Apr 15, 2026
Strangely, the graalvm GCB job did not trigger on the
google-cloud-shared-dependencies/v3.61.0tagchingor13 commentedon Apr 16, 2026
We determined that the trigger had a file filter and the last tag did not have files matching the pattern. This file filter is removed. This should be fixed, but will verify the next time the tag is created
build: create additional tags on release (#12811)