Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00237432374343454434541.031596315960750507851785117992db9fa94452801a1963cf1b4f143869b919443902db9fa94452801a1963cf1b4f143869b91944390origin/main2db9fa94452801a1963cf1b4f143869b919443902db9fa94452801a1963cf1b4f143869b91944390origin/main2db9fa94452801a1963cf1b4f143869b919443902db9fa94452801a1963cf1b4f143869b91944390origin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1799/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1799/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1799/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1799/testsfalse#17994345449176seed #17991799falsefalse17993694166SUCCESS1782118587789https://do.pingcap.net/jenkins/job/seed/1799/default-qfpkftekton/v1/tasks/delivery/pingcap-notify-to-update-ops-tidbx.yamltekton/v1/triggers/triggers/env-gcp/_/notify/update-ops-when-tidbx-image-distributed-to-clouds.yaml2db9fa94452801a1963cf1b4f143869b919443901782118552000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comci(tekton): delegate Ops API logic to publisher service (#4639) This pull request simplifies and streamlines the process for updating Ops with new image deliveries in the Tekton pipeline for TiDB Cloud. The main change is to replace the previous logic for updating Ops (which involved multiple functions and direct config file handling) with a new, centralized "publisher" API. This makes the update process easier to maintain and more consistent across environments. Additionally, the pipeline parameters and triggers are updated to support this new approach. **Pipeline and API Integration Changes:** * Added a new `publisher-url` parameter (with default value `"https://do2.pingcap.net/publisher"`) to the `pingcap-notify-to-update-ops-tidbx` Tekton task, and updated all relevant argument lists and triggers to pass this parameter. [[1]](diffhunk://#diff-24aa9df5d7b698f89d9844eda814ffdbfbb29bc240d1970f66a767883dee0dafR27-R30) [[2]](diffhunk://#diff-c71b5f036ada5537d38c0720d4747f9f9fa0ca737efc900ca75df98af7851e16R31) [[3]](diffhunk://#diff-c71b5f036ada5537d38c0720d4747f9f9fa0ca737efc900ca75df98af7851e16R53-L58) * Refactored the Ops update logic in the task script to call the publisher API directly, removing complex logic related to config file parsing, component extraction, and individual API calls. The script now posts a simple JSON payload to the publisher and processes the response. **Code and Pipeline Simplification:** * Removed the need for the `ops-config` workspace and related secret from the pipeline triggers, further simplifying configuration management. * Cleaned up the argument passing for the `notify-in-lark-channel` step to match the new approach. These changes will make the pipeline easier to maintain and reduce the chance of errors when updating Ops with new image versions. 2026-06-22 08:55:52 +00002db9fa94452801a1963cf1b4f143869b91944390ci(tekton): delegate Ops API logic to publisher service (#4639)edittekton/v1/tasks/delivery/pingcap-notify-to-update-ops-tidbx.yamledittekton/v1/triggers/triggers/env-gcp/_/notify/update-ops-when-tidbx-image-distributed-to-clouds.yamlgithttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply