Started by GitHub push by ti-chi-bot[bot]00235532355343718437181.032466324660761848912891216257998c722cb113fd1d86cfa546c23a401c1ba6ee07998c722cb113fd1d86cfa546c23a401c1ba6ee0origin/main7998c722cb113fd1d86cfa546c23a401c1ba6ee07998c722cb113fd1d86cfa546c23a401c1ba6ee0origin/main7998c722cb113fd1d86cfa546c23a401c1ba6ee07998c722cb113fd1d86cfa546c23a401c1ba6ee0origin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1625/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1625/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1625/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1625/testsfalse#16254371843236seed #16251625falsefalse16253668598SUCCESS1776231517028https://do.pingcap.net/jenkins/job/seed/1625/default-mtq1kpipelines/pingcap/tiflow/latest/pull_dm_integration_test_next_gen.groovy7998c722cb113fd1d86cfa546c23a401c1ba6ee01776231480000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comdm: download tikv-worker for next-gen integration tests (#4524) ## Summary - Download \`tikv-worker\` binary alongside TiKV via \`--tikv-worker=\${OCI_TAG_TIKV}\`. ## Why DM integration tests on next-gen TiDB require a full cluster including a tikv-worker process and a MinIO server that serves DFS storage for TiKV and IA (ingest) for tikv-worker. Without tikv-worker, next-gen TiDB's lightning backend cannot complete ingest backfill (ADD INDEX, IMPORT INTO, etc.), because \`kerneltype.IsNextGen()\` unconditionally routes region jobs through \`objStoreRegionJobWorker\` / \`TiKVWorkerURL\` (see \`pkg/lightning/backend/local/local.go\` in pingcap/tidb). Current build #31 on the next-gen DM pipeline fails G00 (ha_cases) because \`ALTER TABLE ... ADD INDEX\` gets stuck at \"write reorganization\" with \`Put \"http:///write_sst?...\": http: no Host in request URL\` — the TiDB never had a tikv-worker URL to talk to. ## Follow-up A follow-up PR to \`pingcap/tiflow\` will update \`dm/tests/_utils/run_downstream_cluster\` to spin up MinIO + PD (keyspace pre-alloc) + TiKV (API V2 + TTL + DFS) + tikv-worker + SYSTEM TiDB + user keyspace TiDB, mirroring the CDC \`start_tidb_cluster_nextgen\` helper. ## Test plan - [ ] Trigger the next-gen DM integration pipeline from a tiflow PR once both this and the tiflow-side changes land. Ref: \`tests/integration_tests/_utils/start_tidb_cluster_nextgen\` in pingcap/ticdc. 2026-04-15 05:38:00 +00007998c722cb113fd1d86cfa546c23a401c1ba6ee0dm: download tikv-worker for next-gen integration tests (#4524)editpipelines/pingcap/tiflow/latest/pull_dm_integration_test_next_gen.groovygithttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply