feat: add Cloud Build pipeline and evaluation configuration for Cloud SQL MySQL extension#119
Merged
omkargaikwad23 merged 4 commits intomainfrom May 4, 2026
Merged
Conversation
… SQL MySQL extension
omkargaikwad23
added
the
autorelease: pending
prernakakkar-google
approved these changes
May 4, 2026
This was referenced May 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Automated multi-turn EvalBench testing pipeline and Cloud Build CI/CD configuration for the Cloud SQL MySQL extension repository.
Key Changes
cloudbuild.yaml: Implements dynamic PR fetching; limits test execution to PRs withautorelease: pendingorevalslabels; configures dynamic, traceable version mapping (pr-$_PR_NUMBER-evals) for BigQuery metrics.evals/dataset.json: Defines 4 multi-turn scenarios tailored to MySQL-specific tools (list_databases,list_tables,list_table_fragmentation,list_table_stats,get_system_metrics) using dynamic environment placeholders.evals/): Establishesrun_config.yaml,model_config.yaml, andgemini_2.5_pro_model.yamlto track token count consumption, turn count, and end-to-end latency using Vertex AI judges and centralized BigQuery reporting.substitute_env.py: Dynamically injects environment variables into model, run, and dataset configuration files at runtime.