Started by user Yebin Liyebin.li@pingcap.comYebin Li0030827308271212791212791.001116500d4cb89235f7bd5d09a93a09d44be17e0b2022500d4cb89235f7bd5d09a93a09d44be17e0b2022origin/main500d4cb89235f7bd5d09a93a09d44be17e0b2022500d4cb89235f7bd5d09a93a09d44be17e0b2022origin/main500d4cb89235f7bd5d09a93a09d44be17e0b2022500d4cb89235f7bd5d09a93a09d44be17e0b2022origin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#1612127992170seed #1616falsefalse1619110SUCCESS1775186207965https://prow.tidb.net/jenkins/job/seed/16/default-x22tc- .pre-commit-config.yamlf8c70c95b703a7f0d1b730564a58ee04030afe001773841514000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comchore(ci): pre-commit autoupdate (#4365)
<!--pre-commit.ci start-->
updates:
- [github.com/gitleaks/gitleaks: v8.30.0 →
v8.30.1](https://github.com/gitleaks/gitleaks/compare/v8.30.0...v8.30.1)
<!--pre-commit.ci end-->
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
2026-03-18 13:45:14 +0000f8c70c95b703a7f0d1b730564a58ee04030afe00chore(ci): pre-commit autoupdate (#4365)edit.pre-commit-config.yaml
- scripts/flow/build/versioning-strategy.test.tsscripts/flow/build/versioning-strategy.ts0c838c8236177c8007cc1688dfc9def1652477411773842268000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfix(scripts): keep release.<n> version unchanged in versioning strategy (#4373)
This pull request updates the versioning strategy logic and its tests to
better handle release versions with pre-release identifiers. The main
change is that versions with a pre-release tag matching the pattern
`release.<number>` are now recognized and handled differently, ensuring
the published version matches the git tag.
Versioning logic improvements:
* Updated `compute` function in `versioning-strategy.ts` to add a check
for pre-release tags matching `release.<number>`, so these versions are
now left unchanged and logged, preventing unnecessary tag or version
changes.
Test updates for versioning behavior:
* Modified test cases in `versioning-strategy.test.ts` to expect the
published version to be `v8.5.4-release.1` instead of `v8.5.4-pre` when
the git version is `v8.5.4-release.1` and the branch is `release-8.5` or
both `master` and `release-8.5`.
[[1]](diffhunk://#diff-9457acf03916f61345de345c9b6d6ec57c0416f5248090b2a7839cbef981f108L60-R60)
[[2]](diffhunk://#diff-9457acf03916f61345de345c9b6d6ec57c0416f5248090b2a7839cbef981f108L70-R69)
2026-03-18 13:57:48 +00000c838c8236177c8007cc1688dfc9def165247741fix(scripts): keep release.<n> version unchanged in versioning strategyeditscripts/flow/build/versioning-strategy.tseditscripts/flow/build/versioning-strategy.test.ts
- prow-jobs/pingcap-inc/tidb/release-presubmits.yamlpipelines/pingcap-inc/tidb/release-8.5/pull_build.groovypipelines/pingcap-inc/tidb/release-8.5/pull_check2.groovypipelines/pingcap-inc/tidb/release-8.5/pull_check.groovypipelines/pingcap-inc/tidb/release-8.5/pod-pull_check.yamlpipelines/pingcap-inc/tidb/release-8.5/pod-pull_check2.yamllibraries/tipipeline/vars/prow.groovyf93d8391b8a286642eef198a692006c4cedace691773881297000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comchore(pipeline) migrate tidb pull check and check2 to gcp and moidfy codecov upload (#4372)
## What changed
This PR migrates `release-8.5/pull_check` to GCP-ready runtime and
removes key dependencies on legacy IDC paths.
### 1) pull_check pod/runtime migration
- File: `pipelines/pingcap-inc/tidb/release-8.5/pod-pull_check.yaml`
- Changes:
- Switch build image from `hub.pingcap.net/...` to GAR:
-
`us-docker.pkg.dev/pingcap-testing-account/internal/test/wangweizhen/tidb_image:go12320241009`
- Set GOPROXY to GAR remote go proxy:
-
`https://us-go.pkg.dev/pingcap-testing-account/go-proxy-remote|https://proxy.golang.org,direct`
- Remove legacy PVC-based caches
(`gocache/gopathcache/bazel-out-lower/bazel-out-overlay`)
- Use `ConfigMap bazel` instead of secret mount for `/data/`
verify in
https://prow.tidb.net/jenkins/job/pingcap-inc/job/tidb/job/release-8.5/job/pull_check2/9/console
https://prow.tidb.net/jenkins/job/pingcap-inc/job/tidb/job/release-8.5/job/pull_check/10/
2026-03-19 00:48:17 +0000f93d8391b8a286642eef198a692006c4cedace69chore(pipeline) migrate tidb pull check and check2 to gcp and moidfyeditpipelines/pingcap-inc/tidb/release-8.5/pod-pull_check.yamleditlibraries/tipipeline/vars/prow.groovyeditpipelines/pingcap-inc/tidb/release-8.5/pull_build.groovyeditpipelines/pingcap-inc/tidb/release-8.5/pod-pull_check2.yamleditpipelines/pingcap-inc/tidb/release-8.5/pull_check.groovyeditprow-jobs/pingcap-inc/tidb/release-presubmits.yamleditpipelines/pingcap-inc/tidb/release-8.5/pull_check2.groovy
- pipelines/pingcap-inc/tidb/release-8.5/pod-pull_unit_test.yamlpipelines/pingcap-inc/tidb/release-8.5/pod-pull_mysql_test.yamlpipelines/pingcap-inc/tidb/release-8.5/pod-pull_integration_br_test.yamlpipelines/pingcap-inc/tidb/release-8.5/pull_unit_test.groovypipelines/pingcap-inc/tidb/release-8.5/pull_integration_br_test.groovy6ffee2170146050d68179a0a56cde16dca067c4c1773891812000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comchore(pipeline) migrate tidb pull unit test and pull integration test to GCP (#4374)
## Summary
This PR migrates `pingcap-inc` CI jobs (with focus on
`tidb/release-8.5`) to the GCP execution path and aligns pipeline
behavior with the new infra dependencies (GCS/GAR-based flow), while
updating shared CI helpers used by these jobs.
## Scope
- Introduce `pingcap-inc` presubmit job definitions and job entrypoints.
- Add/migrate `pingcap-inc/tidb/release-8.5` pipelines and pod specs to
GCP-ready configs.
- Update shared pipeline library behavior for coverage upload and common
CI runtime compatibility.
- Keep temporary Bazel deps URL hotfix logic in CI layer for replay/job
stability before upstream tidb repo cleanup is fully landed.
2026-03-19 03:43:32 +00006ffee2170146050d68179a0a56cde16dca067c4cchore(pipeline) migrate tidb pull unit test and pull integration test toeditpipelines/pingcap-inc/tidb/release-8.5/pod-pull_unit_test.yamleditpipelines/pingcap-inc/tidb/release-8.5/pod-pull_integration_br_test.yamleditpipelines/pingcap-inc/tidb/release-8.5/pull_integration_br_test.groovyeditpipelines/pingcap-inc/tidb/release-8.5/pod-pull_mysql_test.yamleditpipelines/pingcap-inc/tidb/release-8.5/pull_unit_test.groovy
- prow-jobs/pingcap-inc/tidb/release-presubmits.yamlpipelines/pingcap-inc/tidb/release-8.5/pod-pull_integration_e2e_test.yamlpipelines/pingcap-inc/tidb/release-8.5/pull_integration_e2e_test.groovypipelines/pingcap-inc/tidb/release-8.5/pull_unit_test_ddlv1.groovy70d941189eb397955e2ee78554b5c72bca9b442a1773892556000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comchore(pipeline) migrate tidb pull integration e2e and pull_unit_test_ddlv1 to gcp (#4375)
## What
This PR migrates `pingcap-inc/tidb` (release-8.5) CI jobs to the GCP
execution path and aligns related CI runtime behavior with the new infra
setup (GCS/GAR based).
### Main changes
1. Add/enable `pingcap-inc` presubmit definitions
- `prow-jobs/pingcap-inc/tidb/release-presubmits.yaml`
- `prow-jobs/pingcap-inc/tiflow/release-presubmits.yaml`
- `prow-jobs/pingcap-inc/ticdc/release-presubmits.yaml`
2026-03-19 03:55:56 +000070d941189eb397955e2ee78554b5c72bca9b442achore(pipeline) migrate tidb pull integration e2e andeditpipelines/pingcap-inc/tidb/release-8.5/pull_integration_e2e_test.groovyeditpipelines/pingcap-inc/tidb/release-8.5/pull_unit_test_ddlv1.groovyeditprow-jobs/pingcap-inc/tidb/release-presubmits.yamleditpipelines/pingcap-inc/tidb/release-8.5/pod-pull_integration_e2e_test.yaml
- prow-jobs/pingcap/tiflow/latest-presubmits.yamlprow-jobs/pingcap/ticdc/latest-presubmits.yamlprow-jobs/pingcap/ticdc/latest-presubmits-next-gen.yamlpipelines/pingcap/tiflow/latest/pod-ghpr_verify.yaml2572069dad9bd4b7be11fdf88c0451387fc982d41773987593000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfeat: update go1.25.8 toolchain pin for tiflow/ticdc unit jobs (#4376)
## Summary
This PR update image to mix Go patch toolchain artifacts (`go1.25.8` vs
older `go tool`) that cause compile failures in PR jobs.
## Why
Some jobs are still running in environments/images that are not fully
aligned to Go `1.25.8`, while repo-side changes already pull `1.25.8`
artifacts. This can trigger errors like:
```text
compile: version "go1.25.8" does not match go tool version "go1.25.x"
```
## replay test
https://github.com/pingcap/ticdc/pull/4467
-
https://prow.tidb.net/view/gs/prow-tidb-logs/pr-logs/pull/pingcap_ticdc/4467/pull-unit-test/2034863608625631232
-
https://prow.tidb.net/view/gs/prow-tidb-logs/pr-logs/pull/pingcap_ticdc/4467/pull-unit-test/2034863608625631232
https://github.com/pingcap/tiflow/pull/12560
-
https://prow.tidb.net/view/gs/prow-tidb-logs/pr-logs/pull/pingcap_tiflow/12560/pull-unit-test-cdc/2034866305454051328
-
https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Fghpr_verify/detail/ghpr_verify/4500/pipeline/
Signed-off-by: lyb <yebin.li@pingcap.com>
2026-03-20 06:19:53 +00002572069dad9bd4b7be11fdf88c0451387fc982d4feat: update go1.25.8 toolchain pin for tiflow/ticdc unit jobs (#4376)editprow-jobs/pingcap/ticdc/latest-presubmits.yamleditpipelines/pingcap/tiflow/latest/pod-ghpr_verify.yamleditprow-jobs/pingcap/ticdc/latest-presubmits-next-gen.yamleditprow-jobs/pingcap/tiflow/latest-presubmits.yaml
- pipelines/pingcap/tidb/release-8.1/pod-ghpr_check2.yamlb797510558d1996f3db1e90b57720675945a1ac31774011776000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfix(yaml) tidb/release-8.1 move utils sidecar from volumes to containers in ghpr_check2 pod (#4378)
fix yaml format
Fix the pod template used by `pingcap/tidb/release-8.1/ghpr_check2` by
moving the `utils` sidecar definition from `spec.volumes` to
`spec.containers`.
2026-03-20 13:02:56 +0000b797510558d1996f3db1e90b57720675945a1ac3fix(yaml) tidb/release-8.1 move utils sidecar from volumes to containerseditpipelines/pingcap/tidb/release-8.1/pod-ghpr_check2.yaml
- prow-jobs/pingcap/tidb-engine-ext/release-6.1-latest-presubmits.yamlprow-jobs/pingcap/tidb-binlog/latest-presubmits.yamlprow-jobs/tikv/pd/release-6.1-presubmits.yamlprow-jobs/tikv/rust-rocksdb/latest-presubmits.yamlprow-jobs/pingcap/tidb-engine-ext/latest-presubmits.yamlprow-jobs/tikv/raft-engine/presubmits.yamlprow-jobs/ti-community-infra/prow/presubmits.yaml582f4a987c2b19ca2cc9dc12e77aee68b50aae4b1774193181000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comMigrate prow kubernetes jobs from `gcp-prow-ksyun` to `default` cluster (#4340)
Prow's default cluster is `default`. Jobs pinned to `gcp-prow-ksyun`
need to be migrated by dropping the `cluster` field and removing
dependencies on PVCs that don't exist in the default cluster.
## Changes
- **Remove `cluster: gcp-prow-ksyun`** from all affected jobs (7 files)
— omitting the field defaults to `default` cluster
- **Remove go mod cache dependencies** (env vars
`GO_PROXY`/`GOMODCACHE`, `gomod-cache` PVC volumeMounts/volumes) from
jobs in `tidb-binlog` and `tikv/pd`
- **Remove cargo cache PVC volumes** from `tikv/raft-engine` jobs where
volumeMounts were already commented out (orphaned declarations)
- **Remove cargo cache volumeMounts/volumes** from `tidb-engine-ext`
jobs (both `latest` and `release-6.1`)
## Pending image migrations (`hub.pingcap.net`)
The following jobs still reference internal `hub.pingcap.net` images
that need to be migrated to a public registry — marked with
`TODO(@wuhuizuo)`:
| File | Image |
|------|-------|
| `pingcap/tidb-engine-ext/latest-presubmits.yaml` |
`hub.pingcap.net/tiflash/tiflash-llvm-base:amd64` |
| `pingcap/tidb-engine-ext/release-6.1-latest-presubmits.yaml` |
`hub.pingcap.net/tiflash/tiflash-llvm-base:amd64` |
| `pingcap/tidb-binlog/latest-presubmits.yaml` |
`hub.pingcap.net/jenkins/centos7_golang-1.21:latest`,
`hub.pingcap.net/jenkins/zookeeper`, `hub.pingcap.net/jenkins/kafka` |
| `tikv/pd/release-6.1-presubmits.yaml` |
`hub.pingcap.net/ee/ci/base:v20230803-go1.19.12` |
<!-- START COPILOT ORIGINAL PROMPT -->
<details>
<summary>Original prompt</summary>
>
> ----
>
> *This section details on the original issue you should resolve*
>
> <issue_title>Migrate prow kubernetes type jobs which run on cluster
`gcp-prow-ksyun` to `default` cluster</issue_title>
> <issue_description>prow job default cluster is `default`, so when we
migrate them, we can just delete the `cluster` field in prow job. And
some additional changes we need to make:
>
> 1. when the job use go build or go mod cache env vars and volume and
volume mounts, please delete it.
> 2. when use images from hub.pingcap.net, your should add a task item
in the pull request description and assign the pr to @wuhuizuo and add
label "help wanted" to request help.
>
> </issue_description>
>
> ## Comments on the Issue (you are @copilot in this section)
>
> <comments>
> </comments>
>
</details>
<!-- START COPILOT CODING AGENT SUFFIX -->
- Fixes PingCAP-QE/ci#4339
<!-- START COPILOT CODING AGENT TIPS -->
---
🔒 GitHub Advanced Security automatically protects Copilot coding agent
pull requests. You can protect all pull requests by enabling Advanced
Security for your repositories. [Learn more about Advanced
Security.](https://gh.io/cca-advanced-security)
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: wuhuizuo <2574558+wuhuizuo@users.noreply.github.com>
2026-03-22 15:26:21 +0000582f4a987c2b19ca2cc9dc12e77aee68b50aae4bMigrate prow kubernetes jobs from `gcp-prow-ksyun` to `default` clustereditprow-jobs/ti-community-infra/prow/presubmits.yamleditprow-jobs/tikv/raft-engine/presubmits.yamleditprow-jobs/pingcap/tidb-engine-ext/release-6.1-latest-presubmits.yamleditprow-jobs/pingcap/tidb-engine-ext/latest-presubmits.yamleditprow-jobs/tikv/pd/release-6.1-presubmits.yamleditprow-jobs/tikv/rust-rocksdb/latest-presubmits.yamleditprow-jobs/pingcap/tidb-binlog/latest-presubmits.yaml
- pipelines/pingcap/tidb/release-7.5/pod-pull_integration_binlog_test.yamlpipelines/pingcap/tidb/release-7.1/pod-pull_integration_binlog_test.yamlpipelines/pingcap/tidb/release-6.4/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-7.0/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-6.1/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-7.3/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-6.5-20241101-v6.5.7/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-8.2/pod-pull_check2.yamlpipelines/pingcap/tidb/release-7.2/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-6.5-with-kv-timeout-feature/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-7.6/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-6.3/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-6.5/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-8.1/pod-pull_integration_binlog_test.yamlpipelines/pingcap/tidb/release-7.4/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-8.4/pod-pull_check2.yamlpipelines/pingcap/tidb/latest/pod-periodics_integration_test.yamlpipelines/pingcap/tidb/release-6.1/pod-pull_integration_binlog_test.yamlpipelines/pingcap/tidb/release-8.0/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-7.1/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-6.5/pod-pull_integration_binlog_test.yamlpipelines/pingcap/tidb/release-6.2/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-8.3/pod-pull_check2.yamlpipelines/pingcap/tidb/release-6.6/pod-ghpr_check2.yamlpipelines/pingcap/tidb/release-7.5/pod-ghpr_check2.yaml73ef99cc5bd2073b71eb7fc816ebc6098df791081774232190000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfix(Jenkins yaml) move utils sidecar from volumes to containers in ghpr_check2 pod (#4379)
Some tidb pod templates incorrectly defined the `utils` sidecar under
`spec.volumes`
(with container-only fields like image/tty/resources), which breaks pod
deserialization
in Jenkins/Fabric8 (e.g. ImageVolumeSource parse errors).
This change moves the `utils` block to `spec.containers` across affected
templates,
including release-7.5/release-8.1 ghpr_check2 and other similarly
affected pod files.
2026-03-23 02:16:30 +000073ef99cc5bd2073b71eb7fc816ebc6098df79108fix(Jenkins yaml) move utils sidecar from volumes to containers ineditpipelines/pingcap/tidb/release-6.5-with-kv-timeout-feature/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-6.4/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-7.6/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-8.1/pod-pull_integration_binlog_test.yamleditpipelines/pingcap/tidb/release-7.0/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-6.1/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-8.4/pod-pull_check2.yamleditpipelines/pingcap/tidb/release-7.1/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-6.5-20241101-v6.5.7/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-6.2/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-6.6/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-7.3/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-7.2/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-6.5/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-7.5/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-7.4/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-8.3/pod-pull_check2.yamleditpipelines/pingcap/tidb/latest/pod-periodics_integration_test.yamleditpipelines/pingcap/tidb/release-6.3/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/release-6.5/pod-pull_integration_binlog_test.yamleditpipelines/pingcap/tidb/release-8.2/pod-pull_check2.yamleditpipelines/pingcap/tidb/release-7.1/pod-pull_integration_binlog_test.yamleditpipelines/pingcap/tidb/release-7.5/pod-pull_integration_binlog_test.yamleditpipelines/pingcap/tidb/release-6.1/pod-pull_integration_binlog_test.yamleditpipelines/pingcap/tidb/release-8.0/pod-ghpr_check2.yaml
- pipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/test-pod.yamlprow-jobs/tidbcloud/cloud-storage-engine/latest-presubmits-next-gen.yamlpipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/main-pod.yamlpipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/pipeline.groovy4b455e94cff8f09040a8c23ebdd141521370bea81774236021000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comchore(pipeline) next-gen migrate to GCP (#4377)
## Summary
Migrate
`tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen`
to GCP runtime path, and keep migration-specific hotfixes scoped to this
job.
## Why Temporary Skips
- These two cases are currently noisy/flaky under realcluster migration
validation (resource pressure / cluster bootstrap instability), and they
block signal for infra migration readiness.
- The skip is explicitly temporary and scoped to this job only.
verify in
https://prow.tidb.net/jenkins/job/tidbcloud/job/cloud-storage-engine/job/dedicated/job/pull_integration_realcluster_test_next_gen/14/
2026-03-23 03:20:21 +00004b455e94cff8f09040a8c23ebdd141521370bea8chore(pipeline) next-gen migrate to GCP (#4377)editpipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/main-pod.yamleditprow-jobs/tidbcloud/cloud-storage-engine/latest-presubmits-next-gen.yamleditpipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/pipeline.groovyeditpipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/test-pod.yaml
- pipelines/pingcap/tiflow/latest/pod-pull_cdc_integration_kafka_test.yamlpipelines/pingcap/tiflow/latest/pull_syncdiff_integration_test.groovypipelines/pingcap/tiflow/latest/pull_cdc_integration_test.groovypipelines/pingcap/tiflow/latest/pull_cdc_integration_pulsar_test.groovyprow-jobs/pingcap/tiflow/latest-postsubmits.yamlprow-jobs/pingcap/tiflow/latest-presubmits.yamlpipelines/pingcap/tiflow/latest/pull_cdc_integration_storage_test.groovypipelines/pingcap/tiflow/latest/pull_dm_compatibility_test.groovypipelines/pingcap/tiflow/latest/pull_cdc_integration_kafka_test.groovypipelines/pingcap/tiflow/latest/pod-pull_dm_integration_test.yamlpipelines/pingcap/tiflow/latest/pod-pull_cdc_integration_test.yamlpipelines/pingcap/tiflow/latest/pod-pull_cdc_integration_pulsar_test.yamlpipelines/pingcap/tiflow/latest/pull_dm_integration_test.groovypipelines/pingcap/tiflow/latest/pod-pull_dm_compatibility_test.yamlpipelines/pingcap/tiflow/latest/pod-pull_cdc_integration_build.yamlpipelines/pingcap/tiflow/latest/pod-pull_syncdiff_integration_test.yamlpipelines/pingcap/tiflow/latest/pod-pull_cdc_integration_storage_test.yaml14a40ac952f3e430e73877df7e3c2e493129a28c1774250409000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comci(tiflow): migrate latest Jenkins jobs to GCP (#4367)
## Summary
- keep and refine `pingcap/tiflow` **latest** migration changes for
Jenkins-on-GCP
- complete latest DM/syncdiff migration alignment with existing migrated
jobs:
- use `container("utils")` + OCI artifact downloader
- add `utils` container in DM pod templates
- avoid broad `chmod` on OCI-downloaded root-owned files (fixes replay
failure)
## Scope Decision
- This PR now migrates **latest only**.
- `release-8.5` migration will be handled in a separate follow-up PR.
## Replay tests
-
https://prow.tidb.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Fpull_cdc_integration_kafka_test/detail/pull_cdc_integration_kafka_test/5/pipeline/
-
https://prow.tidb.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Fpull_cdc_integration_pulsar_test/detail/pull_cdc_integration_pulsar_test/2/pipeline/
-
https://prow.tidb.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Fpull_cdc_integration_storage_test/detail/pull_cdc_integration_storage_test/2/pipeline/
-
https://prow.tidb.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Fpull_cdc_integration_test/detail/pull_cdc_integration_test/2/pipeline/
-
https://prow.tidb.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Fghpr_verify/detail/ghpr_verify/3/pipeline
-
https://prow.tidb.net/jenkins/job/pingcap/job/tiflow/job/merged_unit_test/2/
-
https://prow.tidb.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Fpull_dm_compatibility_test/detail/pull_dm_compatibility_test/9/pipeline/
-
https://prow.tidb.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Fpull_dm_integration_test/detail/pull_dm_integration_test/8/pipeline/
-
https://prow.tidb.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Fpull_syncdiff_integration_test/detail/pull_syncdiff_integration_test/6/pipeline/
2026-03-23 07:20:09 +000014a40ac952f3e430e73877df7e3c2e493129a28cci(tiflow): migrate latest Jenkins jobs to GCP (#4367)editpipelines/pingcap/tiflow/latest/pod-pull_cdc_integration_test.yamleditpipelines/pingcap/tiflow/latest/pull_cdc_integration_storage_test.groovyeditpipelines/pingcap/tiflow/latest/pull_dm_compatibility_test.groovyeditpipelines/pingcap/tiflow/latest/pull_cdc_integration_test.groovyeditprow-jobs/pingcap/tiflow/latest-presubmits.yamleditpipelines/pingcap/tiflow/latest/pod-pull_cdc_integration_pulsar_test.yamladdpipelines/pingcap/tiflow/latest/pod-pull_cdc_integration_build.yamleditpipelines/pingcap/tiflow/latest/pod-pull_cdc_integration_kafka_test.yamleditpipelines/pingcap/tiflow/latest/pull_dm_integration_test.groovyeditpipelines/pingcap/tiflow/latest/pod-pull_cdc_integration_storage_test.yamleditpipelines/pingcap/tiflow/latest/pod-pull_dm_compatibility_test.yamleditpipelines/pingcap/tiflow/latest/pull_cdc_integration_pulsar_test.groovyeditprow-jobs/pingcap/tiflow/latest-postsubmits.yamleditpipelines/pingcap/tiflow/latest/pod-pull_dm_integration_test.yamleditpipelines/pingcap/tiflow/latest/pod-pull_syncdiff_integration_test.yamleditpipelines/pingcap/tiflow/latest/pull_cdc_integration_kafka_test.groovyeditpipelines/pingcap/tiflow/latest/pull_syncdiff_integration_test.groovy
- pipelines/pingcap/tiflow/release-8.5/ghpr_verify.groovypipelines/pingcap/tiflow/release-8.5/pod-ghpr_verify.yamlprow-jobs/pingcap/tiflow/release-8.5-presubmits.yamld5da7f69047669915009f50e306d9f4666e893f11774251963000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comci(tiflow): migrate release-8.5 ghpr_verify to gcp (#4380)
## Summary
- migrate pipelines/pingcap/tiflow/release-8.5/ghpr_verify.groovy to GCP
- update tiflow pull-unit-test-cdc-8.5 job image to mix Go patch
toolchain artifacts (go1.25.8 vs older go tool) that cause compile
failures
## Replay Test
-
https://prow.tidb.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflow%2Frelease-8.5%2Fghpr_verify/detail/ghpr_verify/6/pipeline/
-
https://prow.tidb.net/view/gs/prow-tidb-logs/pr-logs/pull/pingcap_tiflow/12566/pull-unit-test-cdc-8.5/2035968598681325568
---------
Signed-off-by: lyb <yebin.li@pingcap.com>
2026-03-23 07:46:03 +0000d5da7f69047669915009f50e306d9f4666e893f1ci(tiflow): migrate release-8.5 ghpr_verify to gcp (#4380)editpipelines/pingcap/tiflow/release-8.5/ghpr_verify.groovyeditpipelines/pingcap/tiflow/release-8.5/pod-ghpr_verify.yamleditprow-jobs/pingcap/tiflow/release-8.5-presubmits.yaml
- pipelines/tikv/tikv/latest/pull_unit_test.groovypipelines/tikv/tikv/release-8.5/pod-pull_unit_test.yamlpipelines/tikv/tikv/release-9.0-beta/pull_unit_test.groovypipelines/tikv/tikv/latest/pod-pull_unit_test.yamlpipelines/tikv/tikv/release-9.0-beta/pod-pull_unit_test.yamlpipelines/tikv/tikv/release-8.5/pull_unit_test.groovye76953d3e1fe5fdd35c1520e6b6ca6a84b1ad1cb1774413321000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfeat(CI) update tikv pull ut job CI image (#4382)
update CI image due to https://github.com/PingCAP-QE/artifacts/pull/918
https://github.com/PingCAP-QE/artifacts/pull/917
2026-03-25 04:35:21 +0000e76953d3e1fe5fdd35c1520e6b6ca6a84b1ad1cbfeat(CI) update tikv pull ut job CI image (#4382)editpipelines/tikv/tikv/release-8.5/pull_unit_test.groovyeditpipelines/tikv/tikv/latest/pull_unit_test.groovyeditpipelines/tikv/tikv/release-8.5/pod-pull_unit_test.yamleditpipelines/tikv/tikv/release-9.0-beta/pull_unit_test.groovyeditpipelines/tikv/tikv/latest/pod-pull_unit_test.yamleditpipelines/tikv/tikv/release-9.0-beta/pod-pull_unit_test.yaml
- prow-jobs/tikv/tikv/latest-presubmits.yaml2f196bc1f65ac7b4da03c51e91b58487fd1a78881774417590000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfeat(CI) update pull-clippy-linux job base image (#4383)
update base image due to
https://github.com/PingCAP-QE/artifacts/pull/917
2026-03-25 05:46:30 +00002f196bc1f65ac7b4da03c51e91b58487fd1a7888feat(CI) update pull-clippy-linux job base image (#4383)editprow-jobs/tikv/tikv/latest-presubmits.yaml
- pipelines/pingcap/tiflash/release-8.5/pull_unit_test.groovy0eba514cad2b3b65ecd0acde5615ddedcab1ea111774497198000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfix(pipelines): make tiflash release-8.5 ut cache prepare idempotent (#4384)
## Summary
- backport the `build_cache_ready` fallback check used in `latest` to
`release-8.5` pull_unit_test pipeline
- make `tests/.build` creation idempotent by changing `mkdir
tests/.build` to `mkdir -p tests/.build`
## Root Cause
In `release-8.5` pull_unit_test, `build_cache_ready` may remain `false`
when cache is restored, so the script enters the cache-miss branch and
runs `mkdir tests/.build`. If the directory already exists from restored
cache, the stage fails with `File exists`.
## Replay Test
-
https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflash%2Frelease-8.5%2Fpull_unit_test/detail/pull_unit_test/356/pipeline/
2026-03-26 03:53:18 +00000eba514cad2b3b65ecd0acde5615ddedcab1ea11fix(pipelines): make tiflash release-8.5 ut cache prepare idempotenteditpipelines/pingcap/tiflash/release-8.5/pull_unit_test.groovy
- tekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-ng.yamlprow-jobs/tidbcloud/cloud-storage-engine/latest-presubmits-next-gen.yamlb993a4432a056246b067384e9c4d48222120942c1774870800000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comci(next-gen): add cloud-engine branch support for cse CI/CD (#4386)
## Summary
- add `^cloud-engine$` to next-gen presubmit branch filters for
`tidbcloud/cloud-storage-engine`
## File Changed
-
`prow-jobs/tidbcloud/cloud-storage-engine/latest-presubmits-next-gen.yaml`
## Why
- enable CI/CD next-gen jobs to be triggered for the `cloud-engine`
branch as requested.
2026-03-30 11:40:00 +0000b993a4432a056246b067384e9c4d48222120942cci(next-gen): add cloud-engine branch support for cse CI/CD (#4386)edittekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-ng.yamleditprow-jobs/tidbcloud/cloud-storage-engine/latest-presubmits-next-gen.yaml
- pipelines/pingcap-inc/tidb/release-8.5/pull_unit_test.groovy2b0190c45e68ee6fa551b39327621c4024be360e1774930377000https://prow.tidb.net/jenkins/user/wuhuizuowuhuizuowuhuizuo@126.comci(pipelines): remove long-time test check
2026-03-31 12:12:57 +08002b0190c45e68ee6fa551b39327621c4024be360eci(pipelines): remove long-time test checkeditpipelines/pingcap-inc/tidb/release-8.5/pull_unit_test.groovy
- tekton/v1/pipelines/pingcap-build-package-darwin.yaml97282c56c4dc687a30c30ba4894c6bceabf415cc1774931080000https://prow.tidb.net/jenkins/user/wuhuizuowuhuizuowuhuizuo@126.compipelines(tekton): Add deliver-images to darwin
Add a conditional deliver-images task to the darwin pipeline.
It is a no-op (echo "skip for darwin") that runs only when params.push
is "true", to explicitly skip image delivery on Darwin builds.
2026-03-31 12:24:40 +080097282c56c4dc687a30c30ba4894c6bceabf415ccpipelines(tekton): Add deliver-images to darwinedittekton/v1/pipelines/pingcap-build-package-darwin.yaml
- tekton/v0/tasks/crane-copy.yamlf3e85d125e426c4898b67c1ef24fbc9c48ca184c1774937766000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comchore(deps): update gcr.io/go-containerregistry/crane docker tag to v0.21.3 (#4369)
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
|
[gcr.io/go-containerregistry/crane](https://images.chainguard.dev/directory/image/static/overview)
([source](https://redirect.github.com/chainguard-images/images/tree/HEAD/images/static))
| patch | `v0.21.1` → `v0.21.3` |
---
> [!WARNING]
> Some dependencies could not be looked up. Check the [Dependency
Dashboard](../issues/1780) for more information.
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/PingCAP-QE/ci).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My42Ni40IiwidXBkYXRlZEluVmVyIjoiNDMuNjYuNCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-03-31 06:16:06 +0000f3e85d125e426c4898b67c1ef24fbc9c48ca184cchore(deps): update gcr.io/go-containerregistry/crane docker tag toedittekton/v0/tasks/crane-copy.yaml
- tekton/v1/tasks/pingcap-git-clone-ext.yamltekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-ng.yamlscripts/flow/build/versioning-strategy.tstekton/v1/tasks/delivery/pingcap-notify-to-update-ops-tidbx.yamltekton/v1/triggers/triggers/env-gcp/_/git-create-tag-build-ng.yamlscripts/flow/build/versioning-strategy.test.tsscripts/flow/build/versioning-strategy.md417be2f1f10f91cf328f847fa75f7a76de8cd4f51774938126000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comci(tekton): support calendar-style nextgen tags (#4387)
## Summary
- accept calendar-style nextgen tags such as `v26.3.1` in the nextgen
tag-build trigger and downstream cloud delivery notifications
- keep plain semver nextgen versions unchanged on `release-nextgen-*`
branches and prefer `release-nextgen-*` when resolving containing
branches for tag-triggered builds
- extend the versioning strategy tests and docs with the new nextgen tag
style
## Testing
- `deno test scripts/flow/build/versioning-strategy.test.ts`
- `ruby -e 'require "yaml"; ...'` against the changed Tekton YAML files
- `git diff --check`
## Notes
- The new plain-semver nextgen tag detection in the tag trigger and Ops
notification path assumes the new nextgen tags use a 2+ digit major, for
example `v26.3.1`.
- `PingCAP-QE/artifacts` still has `delivery.yaml` / package delivery
rules that only match legacy nextgen tags today, so image/package
distribution for `v26.3.1` likely needs a separate follow-up there.
2026-03-31 06:22:06 +0000417be2f1f10f91cf328f847fa75f7a76de8cd4f5ci(tekton): support calendar-style nextgen tags (#4387)editscripts/flow/build/versioning-strategy.mdedittekton/v1/tasks/delivery/pingcap-notify-to-update-ops-tidbx.yamledittekton/v1/tasks/pingcap-git-clone-ext.yamleditscripts/flow/build/versioning-strategy.test.tseditscripts/flow/build/versioning-strategy.tsedittekton/v1/triggers/triggers/env-gcp/_/git-create-tag-build-ng.yamledittekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-ng.yaml
- tekton/v1/triggers/templates/_/build-component-single-platform.yaml.agents/skills/tekton-cd-backend-worker/agents/openai.yaml.agents/skills/tekton-cd-backend-worker/SKILL.mdtekton/v1/triggers/templates/_/build-component-darwin.yamltekton/v1/triggers/templates/_/build-component-linux.yamltekton/v1/tasks/pingcap-git-clone.yamltekton/v1/triggers/templates/_/build-component-all-platforms.yamltekton/v1/pipelines/pingcap-build-package-linux.yamltekton/v1/tasks/kustomization.yamltekton/v1/pipelines/pingcap-build-package-darwin.yaml4e59411c5631d31611013ab08c6deba454e994bd1774953228000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfix(tekton/v1): fix tidb enterprise build for hotfox cases (#4389)
2026-03-31 10:33:48 +00004e59411c5631d31611013ab08c6deba454e994bdfix(tekton/v1): fix tidb enterprise build for hotfox cases (#4389)add.agents/skills/tekton-cd-backend-worker/SKILL.mdedittekton/v1/triggers/templates/_/build-component-single-platform.yamledittekton/v1/tasks/kustomization.yamladd.agents/skills/tekton-cd-backend-worker/agents/openai.yamledittekton/v1/triggers/templates/_/build-component-linux.yamledittekton/v1/triggers/templates/_/build-component-darwin.yamledittekton/v1/pipelines/pingcap-build-package-darwin.yamladdtekton/v1/tasks/pingcap-git-clone.yamledittekton/v1/triggers/templates/_/build-component-all-platforms.yamledittekton/v1/pipelines/pingcap-build-package-linux.yaml
- pipelines/pingcap-inc/tiflash-scripts/latest/pull_regression_test/pipeline.groovyjobs/pingcap-inc/tiflash-scripts/latest/pull_regression_test.groovyjobs/pingcap-inc/tiflash-scripts/latest/pull_schrodinger_test.groovypipelines/pingcap-inc/tiflash-scripts/latest/pull_regression_test/pod.yamlpipelines/pingcap-inc/tiflash-scripts/latest/pull_schrodinger_test/pod.yamlprow-jobs/kustomization.yamlpipelines/pingcap-inc/tiflash-scripts/latest/common/prepare_runtime_and_artifacts.shprow-jobs/pingcap-inc/tiflash-scripts/presubmits.yamlpipelines/pingcap-inc/tiflash-scripts/latest/pull_schrodinger_test/pipeline.groovy6226f953ebe1199aa9720e5af57f44f5ad10d34f1774960548000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comci(tiflash-scripts): add pull-test, regression, and schrodinger jobs (#4391)
## Summary
- add Prow presubmits for `pingcap-inc/tiflash-scripts`:
- native `pull-test`
- jenkins-triggered `pull-regression-test`
- jenkins-triggered `pull-schrodinger-test`
- add Jenkins pipeline + pod templates for `pull_regression_test` and
`pull_schrodinger_test`
- add CI-side runtime and artifact preparation script for
regression/schrodinger pipelines
- keep Jenkins job DSL minimal for Prow-triggered execution
## Scope
-
`pipelines/pingcap-inc/tiflash-scripts/latest/common/prepare_runtime_and_artifacts.sh`
- `jobs/pingcap-inc/tiflash-scripts/latest/pull_regression_test.groovy`
- `jobs/pingcap-inc/tiflash-scripts/latest/pull_schrodinger_test.groovy`
-
`pipelines/pingcap-inc/tiflash-scripts/latest/pull_regression_test/pipeline.groovy`
-
`pipelines/pingcap-inc/tiflash-scripts/latest/pull_regression_test/pod.yaml`
-
`pipelines/pingcap-inc/tiflash-scripts/latest/pull_schrodinger_test/pipeline.groovy`
-
`pipelines/pingcap-inc/tiflash-scripts/latest/pull_schrodinger_test/pod.yaml`
- `prow-jobs/pingcap-inc/tiflash-scripts/presubmits.yaml`
- `prow-jobs/kustomization.yaml`
## Issue Link
- Parent tracker: #3339
- tiflash-scripts sub-issue: #4307
- regression sub-issue: #4357
- schrodinger sub-issue: #4358
2026-03-31 12:35:48 +00006226f953ebe1199aa9720e5af57f44f5ad10d34fci(tiflash-scripts): add pull-test, regression, and schrodinger jobsaddjobs/pingcap-inc/tiflash-scripts/latest/pull_regression_test.groovyaddjobs/pingcap-inc/tiflash-scripts/latest/pull_schrodinger_test.groovyaddpipelines/pingcap-inc/tiflash-scripts/latest/pull_schrodinger_test/pod.yamladdpipelines/pingcap-inc/tiflash-scripts/latest/pull_schrodinger_test/pipeline.groovyaddpipelines/pingcap-inc/tiflash-scripts/latest/pull_regression_test/pipeline.groovyeditprow-jobs/kustomization.yamladdprow-jobs/pingcap-inc/tiflash-scripts/presubmits.yamladdpipelines/pingcap-inc/tiflash-scripts/latest/pull_regression_test/pod.yamladdpipelines/pingcap-inc/tiflash-scripts/latest/common/prepare_runtime_and_artifacts.sh
- pipelines/pingcap/tidb/latest/pod-ghpr_mysql_test.yamlprow-jobs/pingcap/tidb/latest-presubmits.yamlpipelines/pingcap/tidb/latest/ghpr_mysql_test.groovy4ce3056a3cb5b524e6fc2bc4efa8a945348d8bbc1775016795000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfeat(pipeline) tidb ghpr_mysql_test job migrate to GCP (#4441)
## Summary
Migrate `pingcap/tidb/ghpr_mysql_test` to GCP runtime and mark the job
as migrated in prow config.
## Changes
1. Update pipeline structure in
`pipelines/pingcap/tidb/latest/ghpr_mysql_test.groovy`
- switch to `agent none` + stage-level k8s agents
- use `yaml pod_label.withCiLabels(POD_TEMPLATE_FILE, REFS)` instead of
`yamlFile`
- merge `Checkout` + `Prepare` into `Checkout & Prepare`
- keep existing latest job behavior (cache keys / ws cache / post
behavior) while applying GCP migration pattern
replay build:
`https://prow.tidb.net/jenkins/job/pingcap/job/tidb/job/ghpr_mysql_test/2`
- result: `SUCCESS`
2026-04-01 04:13:15 +00004ce3056a3cb5b524e6fc2bc4efa8a945348d8bbcfeat(pipeline) tidb ghpr_mysql_test job migrate to GCP (#4441)editpipelines/pingcap/tidb/latest/ghpr_mysql_test.groovyeditpipelines/pingcap/tidb/latest/pod-ghpr_mysql_test.yamleditprow-jobs/pingcap/tidb/latest-presubmits.yaml
- prow-jobs/pingcap/tiflash/latest-presubmits.yaml.ci/replay-prow-job.shprow-jobs/pingcap-qe/ci/presubmits.yamle00d9c849318b5c95bf285dc952d2f68a5a81cb61775017134000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comci(prow): add tiflash sanitizer jobs and replay automation (#4390)
## Summary
- add native Prow presubmits for `pingcap/tiflash` sanitizer workflows:
- `pull-sanitizer-asan`
- `pull-sanitizer-tsan`
- add local replay automation for native Prow jobs
- wire replay automation presubmit in `pingcap-qe/ci`
## Scope
- `.ci/replay-prow-job.sh`
- `prow-jobs/pingcap-qe/ci/presubmits.yaml`
- `prow-jobs/pingcap/tiflash/latest-presubmits.yaml`
## Issue Link
- Parent tracker: #3339
- Sanitizer sub-issue: #4348
- Replay automation sub-issue: #4359
2026-04-01 04:18:54 +0000e00d9c849318b5c95bf285dc952d2f68a5a81cb6ci(prow): add tiflash sanitizer jobs and replay automation (#4390)add.ci/replay-prow-job.sheditprow-jobs/pingcap-qe/ci/presubmits.yamleditprow-jobs/pingcap/tiflash/latest-presubmits.yaml
- pipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/pipeline.groovydca5707636bde8fa5fc179c4e8b2a879537310b31775032398000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfix(pipeline) remove legacy depends (#4444)
remove bazel legacy depends
replay:
https://prow.tidb.net/jenkins/job/tidbcloud/job/cloud-storage-engine/job/dedicated/job/pull_integration_realcluster_test_next_gen/149/console
2026-04-01 08:33:18 +0000dca5707636bde8fa5fc179c4e8b2a879537310b3fix(pipeline) remove legacy depends (#4444)editpipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/pipeline.groovy
- pipelines/pingcap/tidb/latest/pull_integration_realcluster_test_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_light_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy_next_gen/pipeline.groovypipelines/pingcap-qe/tidb-test/latest/pull_integration_jdbc_test_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_light_next_gen/pipeline.groovypipelines/tikv/pd/latest/pull_integration_realcluster_test_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_heavy_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_heavy_next_gen/pipeline.groovypipelines/pingcap/tidb/latest/pull_integration_e2e_test_next_gen/pipeline.groovypipelines/pingcap/tidb/latest/pull_integration_ddl_test_next_gen/pipeline.groovypipelines/pingcap/tiflash/latest/pull_integration_next_gen.groovypipelines/pingcap/tidb/latest/pull_br_integration_test_next_gen/pipeline.groovypipelines/pingcap/tidb/latest/pull_mysql_test_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_heavy_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light_next_gen/pipeline.groovypipelines/pingcap-qe/tidb-test/latest/pull_mysql_test_next_gen/pipeline.groovy702ea2e07a63aad651fb839fa3ec99c782b9f5821775036184000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comci(pipelines): update nextgen trunk branch for CSE repo (#4443)
migrate `dedicated` to `cloud-engine`
Refs #4442
2026-04-01 09:36:24 +0000702ea2e07a63aad651fb839fa3ec99c782b9f582ci(pipelines): update nextgen trunk branch for CSE repo (#4443)editpipelines/pingcap/tidb/latest/pull_mysql_test_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_heavy_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pipeline.groovyeditpipelines/pingcap-qe/tidb-test/latest/pull_mysql_test_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy_next_gen/pipeline.groovyeditpipelines/pingcap/tidb/latest/pull_integration_e2e_test_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light_next_gen/pipeline.groovyeditpipelines/pingcap/tidb/latest/pull_integration_realcluster_test_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_heavy_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_light_next_gen/pipeline.groovyeditpipelines/tikv/pd/latest/pull_integration_realcluster_test_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_light_next_gen/pipeline.groovyeditpipelines/pingcap/tidb/latest/pull_integration_ddl_test_next_gen/pipeline.groovyeditpipelines/pingcap/tiflash/latest/pull_integration_next_gen.groovyeditpipelines/pingcap-qe/tidb-test/latest/pull_integration_jdbc_test_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_heavy_next_gen/pipeline.groovyeditpipelines/pingcap/tidb/latest/pull_br_integration_test_next_gen/pipeline.groovy
- scripts/ops/nextgen/README.mdscripts/ops/nextgen/get-next-gen-exact-image-tags.sh02c2b1d5f4512c9f447e9ab6689d09b380324b431775100003000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfix(nextgen): refresh exact image tag lookup branches (#4446)
## Summary
- update `scripts/ops/nextgen/get-next-gen-exact-image-tags.sh` to use
the newly cut next-gen release branch `release-nextgen-202603` for the
core next-gen repos
- switch the TiKV/CSE trunk lookup from `dedicated-next-gen` to
`cloud-engine-next-gen`
- sync `scripts/ops/nextgen/README.md` with the current script behavior
and covered registries/tags
## Validation
- `bash -n scripts/ops/nextgen/get-next-gen-exact-image-tags.sh`
- `PATH="$PWD/../.cache/bin:$PATH" shellcheck -S error
scripts/ops/nextgen/get-next-gen-exact-image-tags.sh`
- `git diff --check`
## Notes
- I did not run the script end-to-end against the registry in this
workspace because `gcloud` is not installed here, so the registry login
step cannot be exercised locally.
2026-04-02 03:20:03 +000002c2b1d5f4512c9f447e9ab6689d09b380324b43fix(nextgen): refresh exact image tag lookup branches (#4446)editscripts/ops/nextgen/README.mdeditscripts/ops/nextgen/get-next-gen-exact-image-tags.sh
- pipelines/pingcap/tidb/latest/pull_integration_realcluster_test_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_light_next_gen/pipeline.groovypipelines/pingcap-qe/tidb-test/latest/pull_integration_jdbc_test_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_light_next_gen/pipeline.groovypipelines/tikv/pd/latest/pull_integration_realcluster_test_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_heavy_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_heavy_next_gen/pipeline.groovypipelines/pingcap/tidb/latest/pull_integration_e2e_test_next_gen/pipeline.groovypipelines/pingcap/tidb/latest/pull_integration_ddl_test_next_gen/pipeline.groovypipelines/pingcap/tiflash/latest/pull_integration_next_gen.groovypipelines/pingcap/tidb/latest/pull_br_integration_test_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_heavy_next_gen/pipeline.groovypipelines/pingcap/tidb/latest/pull_mysql_test_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pipeline.groovypipelines/pingcap-qe/tidb-test/latest/pull_mysql_test_next_gen/pipeline.groovy4adb508592a529a1498d2d8cbf484425029c5c451775104496000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comrevert: rollback nextgen CSE trunk-branch switch (#4450)
## Summary
- revert the 17 pipeline-line changes introduced by `PingCAP-QE/ci#4443`
- restore `dedicated` / `dedicated-next-gen` defaults in the affected
nextgen TiKV-related pipelines
- keep the revert scoped to the original merged change on top of current
`main`
## Why
`#EE-CICD` requested rolling back `ci#4443`. I checked current `main`
first and confirmed the `#4443` edits had not been superseded by later
PRs on those files, so a direct revert is the smallest safe rollback.
## Validation
- `git diff --check origin/main...HEAD`
- `rg -n "cloud-engine(-next-gen)?" <affected files>` returns no matches
after the revert
## Reverts
- PingCAP-QE/ci#4443
- commit `702ea2e07a63aad651fb839fa3ec99c782b9f582`
2026-04-02 12:34:56 +08004adb508592a529a1498d2d8cbf484425029c5c45revert: rollback nextgen CSE trunk-branch switch (#4450)editpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_light_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_heavy_next_gen/pipeline.groovyeditpipelines/pingcap/tidb/latest/pull_integration_e2e_test_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_heavy_next_gen/pipeline.groovyeditpipelines/pingcap/tidb/latest/pull_mysql_test_next_gen/pipeline.groovyeditpipelines/pingcap/tidb/latest/pull_integration_realcluster_test_next_gen/pipeline.groovyeditpipelines/pingcap/tiflash/latest/pull_integration_next_gen.groovyeditpipelines/tikv/pd/latest/pull_integration_realcluster_test_next_gen/pipeline.groovyeditpipelines/pingcap/tidb/latest/pull_integration_ddl_test_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_heavy_next_gen/pipeline.groovyeditpipelines/pingcap-qe/tidb-test/latest/pull_integration_jdbc_test_next_gen/pipeline.groovyeditpipelines/pingcap-qe/tidb-test/latest/pull_mysql_test_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_light_next_gen/pipeline.groovyeditpipelines/pingcap/tidb/latest/pull_br_integration_test_next_gen/pipeline.groovy
- pipelines/pingcap/tidb/release-8.5/pull_integration_lightning_test.groovypipelines/pingcap/tidb/release-8.5/pull_integration_tidb_tools_test.groovypipelines/pingcap/tidb/release-8.5/pull_e2e_test.groovy546e8f338973541b2020f705b78e2bfbaed70c411775104578000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfix(tidb): stabilize release-8.5 artifact prep jobs (#4449)
## Summary
- run release-8.5 `pull_e2e_test` artifact downloads in the `utils`
container so `oras` is available
- make the release-8.5 lightning job tolerate the normalized `tiflash ->
tiflash_dir/tiflash` layout produced by the OCI download helper
- stop chmod'ing every downloaded binary in the release-8.5 tidb-tools
job so root-owned artifacts from the helper do not fail the prepare
stage
## Validation
- `git diff --check`
## Related
- pingcap/tidb#67490
2026-04-02 04:36:18 +0000546e8f338973541b2020f705b78e2bfbaed70c41fix(tidb): stabilize release-8.5 artifact prep jobs (#4449)editpipelines/pingcap/tidb/release-8.5/pull_integration_lightning_test.groovyeditpipelines/pingcap/tidb/release-8.5/pull_integration_tidb_tools_test.groovyeditpipelines/pingcap/tidb/release-8.5/pull_e2e_test.groovy
- pipelines/pingcap/tidb/latest/ghpr_check.groovypipelines/pingcap/tidb/latest/merged_integration_python_orm_test.groovypipelines/pingcap/tidb/latest/pod-ghpr_check.yamlprow-jobs/pingcap/tidb/latest-postsubmits.yamlpipelines/pingcap/tidb/latest/ghpr_check2.groovypipelines/pingcap/tidb/latest/pod-merged_sqllogic_test.yamlpipelines/pingcap/tidb/latest/merged_integration_copr_test.groovypipelines/pingcap/tidb/latest/merged_unit_test_ddlv1.groovypipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/pipeline.groovypipelines/pingcap/tidb/latest/merged_integration_mysql_test.groovypipelines/pingcap/tidb/latest/pod-ghpr_unit_test.yamlpipelines/pingcap/tidb/latest/pod-merged_integration_jdbc_test.yamlpipelines/pingcap/tidb/latest/pod-merged_integration_mysql_test.yamlpipelines/pingcap/tidb/latest/merged_unit_test.groovypipelines/pingcap/tidb/latest/merged_sqllogic_test.groovypipelines/pingcap/tidb/latest/merged_integration_br_test.groovypipelines/pingcap/tidb/latest/pod-merged_common_test.yamlpipelines/pingcap/tidb/latest/ghpr_unit_test.groovypipelines/pingcap/tidb/latest/pod-merged_unit_test.yamlpipelines/pingcap/tidb/latest/pod-ghpr_check2.yamlpipelines/pingcap/tidb/latest/pod-merged_integration_python_orm_test.yamlpipelines/pingcap/tidb/latest/merged_common_test.groovypipelines/pingcap/tidb/latest/pod-merged_integration_lightning_test.yamlpipelines/pingcap/tidb/latest/merged_e2e_test.groovypipelines/pingcap/tidb/latest/ghpr_build/pipeline.groovypipelines/pingcap/tidb/latest/pod-merged_integration_copr_test.yamlpipelines/pingcap/tidb/latest/pod-merged_integration_br_test.yamlpipelines/pingcap/tidb/latest/pod-merged_e2e_test.yamlpipelines/pingcap/tidb/latest/ghpr_build/pod.yaml.ci/replay-prow-job.shprow-jobs/pingcap/tidb/latest-presubmits.yamlpipelines/pingcap/tidb/latest/merged_integration_lightning_test.groovypipelines/pingcap/tidb/latest/pod-merged_unit_test_ddlv1.yamlpipelines/pingcap/tidb/latest/merged_integration_jdbc_test.groovy481eeec3e7c9717ea36cd227d33ca2dba4bc7f1d1775122509000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfeat(pipeline) migrate tidb master branch job to GCP (#4447)
migrate to GCP
1. ghpr_build
2. ghpr_check
3. ghpr_check2
4. ghpr_unit_test
5. merged_common_test
6. merged_eze_test
7. merged_integration_br_test
8. merged_integration_copr_test
9. merged_integration_jdbc_test
10. merged_integration_lightning_test
11. merged_integration_mysql_test
12. merged_integration_python_orm_test
13. merged_sqllogic_test
14. merged_unit_test
15. merged_unit_test_ddlv1
Resolves #4396 #4397 #4398 #4399 #4400
2026-04-02 09:35:09 +0000481eeec3e7c9717ea36cd227d33ca2dba4bc7f1dfeat(pipeline) migrate tidb master branch job to GCP (#4447)editpipelines/pingcap/tidb/latest/pod-merged_common_test.yamleditpipelines/pingcap/tidb/latest/pod-merged_integration_mysql_test.yamleditpipelines/pingcap/tidb/latest/merged_common_test.groovyeditpipelines/pingcap/tidb/latest/pod-merged_e2e_test.yamladdpipelines/pingcap/tidb/latest/pod-merged_unit_test_ddlv1.yamleditprow-jobs/pingcap/tidb/latest-postsubmits.yamleditpipelines/pingcap/tidb/latest/ghpr_unit_test.groovyeditpipelines/pingcap/tidb/latest/merged_integration_br_test.groovyeditpipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/pipeline.groovyeditpipelines/pingcap/tidb/latest/merged_integration_copr_test.groovyedit.ci/replay-prow-job.sheditpipelines/pingcap/tidb/latest/merged_integration_jdbc_test.groovyeditpipelines/pingcap/tidb/latest/ghpr_build/pod.yamleditpipelines/pingcap/tidb/latest/merged_sqllogic_test.groovyeditpipelines/pingcap/tidb/latest/pod-merged_unit_test.yamleditpipelines/pingcap/tidb/latest/pod-ghpr_check.yamleditpipelines/pingcap/tidb/latest/ghpr_check.groovyeditpipelines/pingcap/tidb/latest/ghpr_check2.groovyeditpipelines/pingcap/tidb/latest/merged_integration_python_orm_test.groovyeditpipelines/pingcap/tidb/latest/merged_unit_test_ddlv1.groovyeditpipelines/pingcap/tidb/latest/pod-merged_integration_python_orm_test.yamleditpipelines/pingcap/tidb/latest/merged_unit_test.groovyeditpipelines/pingcap/tidb/latest/pod-merged_integration_lightning_test.yamleditpipelines/pingcap/tidb/latest/pod-merged_integration_br_test.yamleditpipelines/pingcap/tidb/latest/merged_integration_mysql_test.groovyeditpipelines/pingcap/tidb/latest/pod-merged_integration_copr_test.yamleditpipelines/pingcap/tidb/latest/pod-ghpr_unit_test.yamleditpipelines/pingcap/tidb/latest/merged_e2e_test.groovyeditpipelines/pingcap/tidb/latest/pod-merged_integration_jdbc_test.yamleditprow-jobs/pingcap/tidb/latest-presubmits.yamleditpipelines/pingcap/tidb/latest/ghpr_build/pipeline.groovyeditpipelines/pingcap/tidb/latest/merged_integration_lightning_test.groovyeditpipelines/pingcap/tidb/latest/pod-ghpr_check2.yamleditpipelines/pingcap/tidb/latest/pod-merged_sqllogic_test.yaml
- .ci/replay-prow-job.shprow-jobs/pingcap-qe/ci/presubmits.yamlprow-jobs/pingcap-inc/tiflash-scripts/presubmits.yamlprow-jobs/pingcap/tiflash/latest-presubmits.yamljobs/pingcap-inc/tiflash-scripts/aa_folder.groovy8dcd847e003bc2d5c7e0b46463c20da764e1d5601775127069000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comci(prow): stabilize tiflash pull-test and sanitizer jobs (#4445)
## Summary
- stabilize TiFlash native Prow jobs (`pull-test`,
`pull-sanitizer-asan`, `pull-sanitizer-tsan`) based on replay findings
- add missing Jenkins folder declaration for
`pingcap-inc/tiflash-scripts`
- remove unstable Prow replay presubmit (`pull-replay-prow-jobs`) and
remove the complex `.ci/replay-prow-job.sh`
## Key Changes
- `prow-jobs/pingcap-inc/tiflash-scripts/presubmits.yaml`
- patch `integrated/_base/proc.sh` at runtime to tolerate `close failed`
cleanup flakiness
- collect `ops-ti-jenkins-attempt*.log` as artifacts
- run OPS TI flow with one guarded retry after `clean_env` when the
first attempt fails on `close failed`
- `prow-jobs/pingcap/tiflash/latest-presubmits.yaml`
- sanitizer resource memory: `32Gi -> 48Gi`
- ASan: build `-j8`, test `NPROC=8`
- TSan: build `-j6`, test `NPROC=6`
- require `setarch -R` for TSan runtime
- run TSan container as `privileged: true`
- `jobs/pingcap-inc/tiflash-scripts/aa_folder.groovy`
- add Jenkins folder declaration
## Replay Validation
- `pull-test`: success
https://prow.tidb.net/view/gs/prow-tidb-logs/pr-logs/pull/pingcap-inc_tiflash-scripts/2003/pull-test/2039262772029558784
- `pull-sanitizer-asan`: success
https://prow.tidb.net/view/gs/prow-tidb-logs/pr-logs/pull/pingcap_tiflash/10784/pull-sanitizer-asan/2039262777738006528
- `pull-sanitizer-tsan`: success
https://prow.tidb.net/view/gs/prow-tidb-logs/pr-logs/pull/pingcap_tiflash/10784/pull-sanitizer-tsan/2039262783094132736
2026-04-02 10:51:09 +00008dcd847e003bc2d5c7e0b46463c20da764e1d560ci(prow): stabilize tiflash pull-test and sanitizer jobs (#4445)delete.ci/replay-prow-job.shaddjobs/pingcap-inc/tiflash-scripts/aa_folder.groovyeditprow-jobs/pingcap-qe/ci/presubmits.yamleditprow-jobs/pingcap/tiflash/latest-presubmits.yamleditprow-jobs/pingcap-inc/tiflash-scripts/presubmits.yaml
- pipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/pipeline.groovy500d4cb89235f7bd5d09a93a09d44be17e0b20221775185929000https://prow.tidb.net/jenkins/user/noreplynoreplynoreply@github.comfeat(pipeline) disable bazel cache in cse job (#4451)
disable bazel cache in cse job
replay:
https://prow.tidb.net/jenkins/job/tidbcloud/job/cloud-storage-engine/job/dedicated/job/pull_integration_realcluster_test_next_gen/175/
2026-04-03 03:12:09 +0000500d4cb89235f7bd5d09a93a09d44be17e0b2022feat(pipeline) disable bazel cache in cse job (#4451)editpipelines/tidbcloud/cloud-storage-engine/dedicated/pull_integration_realcluster_test_next_gen/pipeline.groovy
githttps://prow.tidb.net/jenkins/user/wuhuizuowuhuizuohttps://prow.tidb.net/jenkins/user/noreplynoreply