Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00179551795551575515751.02556425564077139760776071608dd7dc0392220d9d4e4f5cb29bd7306f8118d9f62dd7dc0392220d9d4e4f5cb29bd7306f8118d9f62origin/maindd7dc0392220d9d4e4f5cb29bd7306f8118d9f62dd7dc0392220d9d4e4f5cb29bd7306f8118d9f62origin/maindd7dc0392220d9d4e4f5cb29bd7306f8118d9f62dd7dc0392220d9d4e4f5cb29bd7306f8118d9f62origin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1608/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1608/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1608/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1608/testsfalse#16085157580415seed #16081608falsefalse16083662908SUCCESS1775817657126https://do.pingcap.net/jenkins/job/seed/1608/default-gp5f7tekton/v1/pipelines/pingcap-build-package-linux.yamldd7dc0392220d9d4e4f5cb29bd7306f8118d9f621775817627000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comtekton: avoid dirty tidb-operator version during image builds (#4503) ## Summary - move the package `release-dir` outside the checked-out source repo in the linux package pipeline - avoid creating an untracked `build/` directory inside component repos before kaniko image builds - fix the `tidb-operator` image version showing `-dirty` when built through the tekton package pipeline ## Root cause `pingcap-build-images` runs in the checked-out repo root and the generated image build script unconditionally creates `RELEASE_WS` before invoking kaniko. The linux package pipeline currently passes `release-dir=build`, so the repo gets an untracked `build/` directory. For `tidb-operator >= 2.0`, image builds use `context: .` plus `image/Dockerfile`, and the Dockerfile runs `./hack/build.sh` inside the repo. `tidb-operator` derives `dirty` from VCS state, so the untracked `build/` directory turns the version into `-dirty`. ## Validation - `yq e '.' tekton/v1/pipelines/pingcap-build-package-linux.yaml >/dev/null` - `git diff --check` - local repro in `pingcap/tidb-operator`: - clean tree => clean version metadata - creating only an untracked `build/` directory => dirty version metadata 2026-04-10 10:40:27 +0000dd7dc0392220d9d4e4f5cb29bd7306f8118d9f62tekton: avoid dirty tidb-operator version during image builds (#4503)edittekton/v1/pipelines/pingcap-build-package-linux.yamlgithttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply