Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00193911939182582825821.0257982579801083806405640516120767f140adb2bd7c8ef74dd1007aef091f4df1a90767f140adb2bd7c8ef74dd1007aef091f4df1a9origin/main0767f140adb2bd7c8ef74dd1007aef091f4df1a90767f140adb2bd7c8ef74dd1007aef091f4df1a9origin/main0767f140adb2bd7c8ef74dd1007aef091f4df1a90767f140adb2bd7c8ef74dd1007aef091f4df1a9origin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1612/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1612/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1612/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1612/testsfalse#16128258255797seed #16121612falsefalse16123665241SUCCESS1776078846810https://do.pingcap.net/jenkins/job/seed/1612/default-ln7h2pipelines/pingcap/tidb/release-8.5/pod-pull_build.yaml0767f140adb2bd7c8ef74dd1007aef091f4df1a91776078816000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comrefactor(pipelines/pingcap/tidb): use ephemeral PVC workspace volume for release-8.5 pull_build (#4509) ## Summary - override the Jenkins kubernetes default workspace volume for `pingcap/tidb/release-8.5/pull_build` - keep the pod definition in YAML instead of configuring `workspaceVolume` in the pipeline DSL - define `spec.volumes[].name=workspace-volume` as an ephemeral `volumeClaimTemplate` - keep this PR scoped to a single high-IO migrated GCP job for phase-1 validation ## Why Migrated Jenkins jobs on GCP currently rely on the kubernetes plugin default workspace volume when `workspaceVolume` is not set explicitly. For large build jobs, that means the workspace lives on node-local ephemeral storage and can be constrained by small-space nodes. For declarative Jenkins pipelines in this repo, keeping pod configuration in the pod YAML is the better maintenance model. This PR therefore validates the rollout pattern by overriding `workspace-volume` directly in the pod template YAML for one representative job first. ## Validation - validated `pipelines/pingcap/tidb/release-8.5/pull_build.groovy` via `.ci/verify-jenkins-pipeline-file.sh` - parsed `pipelines/pingcap/tidb/release-8.5/pod-pull_build.yaml` locally and verified `workspace-volume` resolves to an ephemeral PVC with `storageClassName=hyperdisk-rwo` and `storage=150Gi` - verified the pod YAML still survives the same annotation-style round-trip that `pod_label.withCiLabels(...)` performs 2026-04-13 11:13:36 +00000767f140adb2bd7c8ef74dd1007aef091f4df1a9refactor(pipelines/pingcap/tidb): use ephemeral PVC workspace volume foreditpipelines/pingcap/tidb/release-8.5/pod-pull_build.yamlgithttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply