Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00158291582943611436111.006988698817860bb5d8ffa9d082ac3dd81829bc0f7503b4dec0ce0bb5d8ffa9d082ac3dd81829bc0f7503b4dec0ceorigin/main0bb5d8ffa9d082ac3dd81829bc0f7503b4dec0ce0bb5d8ffa9d082ac3dd81829bc0f7503b4dec0ceorigin/main0bb5d8ffa9d082ac3dd81829bc0f7503b4dec0ce0bb5d8ffa9d082ac3dd81829bc0f7503b4dec0ceorigin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#17864361150115seed #17861786falsefalse17863694121SUCCESS1781761872482https://do.pingcap.net/jenkins/job/seed/1786/default-7tt5mtekton/v1/tasks/delivery/pingcap-notify-to-update-ops-tidbx.yamltekton/v1/triggers/triggers/env-gcp/kustomization.yamltekton/v1/triggers/triggers/env-gcp/_/notify/notified-successful-image-delivery-cloud-tidbx.yamltekton/v1/triggers/triggers/env-gcp/_/notify/update-tcms-when-tidbx-image-distributed-to-clouds.yamltekton/v1/triggers/triggers/env-gcp/_/notify/update-ops-when-tidbx-image-distributed-to-clouds.yaml0bb5d8ffa9d082ac3dd81829bc0f7503b4dec0ce1781761845000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comrefactor(tekton): split tidbx trigger and add tag filter for ops (#4700) ## Summary Refactors the tidbx image delivery notification triggers to improve separation of concerns and add release-tag filtering. ## Changes ### 1. Split combined trigger into two focused triggers The previous `notified-successful-image-delivery-cloud-tidbx` trigger spawned both an ops-update **and** a TCMS-update TaskRun in a single trigger. This meant both tasks shared the same filter conditions, which is not ideal — TCMS should record all image deliveries, but ops should only act on release images. - **`update-ops-when-tidbx-image-distributed-to-clouds`** (renamed from `notified-successful-image-delivery-cloud-tidbx`) - Triggers `pingcap-notify-to-update-ops-tidbx` TaskRun - **`update-tcms-when-tidbx-image-distributed-to-clouds`** (new) - Triggers `pingcap-notify-to-update-tcms-tidbx` TaskRun ### 2. Add image tag validation to ops trigger The ops trigger now validates that **every** image tag matches one of: - `vX.Y.Z` (e.g. `v7.5.1`) - `vX.Y.Z-nextgen` (e.g. `v7.5.1-nextgen`) - `vX.Y.Z-nextgen.YYYYMM.N` (e.g. `v7.5.1-nextgen.202601.1`) Non-release tags (e.g. `v7.5.1-rc`, `latest`) are filtered out and will not trigger ops updates. ### 3. Enable ops update for dev stage The `update-ops-config` step in `pingcap-notify-to-update-ops-tidbx` now runs for both `prod` and `dev` stages (previously only `prod`). ### 4. Update kustomization `kustomization.yaml` updated to reference the two new trigger files and remove the old one. ## Files changed | File | Change | |------|--------| | `tekton/v1/triggers/.../update-ops-when-tidbx-image-distributed-to-clouds.yaml` | Renamed + tag filter + split | | `tekton/v1/triggers/.../update-tcms-when-tidbx-image-distributed-to-clouds.yaml` | New (TCMS extracted from old trigger) | | `tekton/v1/tasks/delivery/pingcap-notify-to-update-ops-tidbx.yaml` | Enable dev stage | | `tekton/v1/triggers/triggers/env-gcp/kustomization.yaml` | Update references | 2026-06-18 05:50:45 +00000bb5d8ffa9d082ac3dd81829bc0f7503b4dec0cerefactor(tekton): split tidbx trigger and add tag filter for ops (#4700)addtekton/v1/triggers/triggers/env-gcp/_/notify/update-tcms-when-tidbx-image-distributed-to-clouds.yamledittekton/v1/tasks/delivery/pingcap-notify-to-update-ops-tidbx.yamldeletetekton/v1/triggers/triggers/env-gcp/_/notify/notified-successful-image-delivery-cloud-tidbx.yamledittekton/v1/triggers/triggers/env-gcp/kustomization.yamladdtekton/v1/triggers/triggers/env-gcp/_/notify/update-ops-when-tidbx-image-distributed-to-clouds.yamlgithttps://do.pingcap.net/jenkins/user/noreplynoreply