Started by GitHub push by ti-chi-bot[bot]0022605226051029641029641.031960319600134924935393531762261bc4f777143c96b2b4140a164530f8f83cd0ac261bc4f777143c96b2b4140a164530f8f83cd0acorigin/main261bc4f777143c96b2b4140a164530f8f83cd0ac261bc4f777143c96b2b4140a164530f8f83cd0acorigin/main261bc4f777143c96b2b4140a164530f8f83cd0ac261bc4f777143c96b2b4140a164530f8f83cd0acorigin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1762/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1762/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1762/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1762/testsfalse#1762102964109407seed #17621762falsefalse17623693690SUCCESS1781189855111https://do.pingcap.net/jenkins/job/seed/1762/default-jl50rtekton/v1/tasks/delivery/pingcap-notify-to-deliver-images-to-cloud-tidbx.yaml261bc4f777143c96b2b4140a164530f8f83cd0ac1781189817000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comrefactor(tekton/v1/tasks): refactor tidbx delivery task to use rotating queue issues (#4677) ## Problem The `pingcap-notify-to-deliver-images-to-cloud-tidbx` task posts `/fid` commands as comments on a **fixed GitHub issue**. GitHub limits issues to 2500 comments, and once reached, the API rejects new comments. Additionally, the old script used `set -e` without `pipefail`, so when `gh issue comment | tee ...` failed, the pipeline's exit code came from `tee` (always 0), silently swallowing the error. ## Solution Replace the fixed-issue approach with an **auto-rotating queue issue** mechanism: - Each stage (`dev`/`prod`) gets a queue issue tracked by a **hierarchical label** `delivery-queue-tidbx/<stage>`. - On each run, the task looks up the current open queue issue for that label. - If the issue has **≥ 2000 comments**, it closes the old issue and creates a new one (rotation). - The `/fid` command is posted as a comment on the current (new or existing) queue issue. - Added `gh label create` as a safety net so the label is auto-created on first use if it doesn't exist in the repo. ### Changes | Before | After | |---|---| | Fixed issue URL from workspace secret (`<stage>_github_issue_url`) | Auto-discovered via label `delivery-queue-tidbx/<stage>` | | No rotation — comments accumulate until 2500 API limit | Auto-rotation at 2000 comments | | `set -e` (pipe exits 0 when `tee` succeeds) | `set -eo pipefail` (fail immediately on pipe error) | | Workspace expects `<stage>_github_issue_url` | Workspace expects `<stage>_github_repo` (e.g. `pingcap/tidb`) | ## Migration The cluster secret `image-delivery-notify-config-tidbx` needs updating: ``` - dev_github_issue_url=https://github.com/.../issues/N + dev_github_repo=pingcap/tidb - prod_github_issue_url=https://github.com/.../issues/M + prod_github_repo=pingcap/tidb ``` 2026-06-11 14:56:57 +0000261bc4f777143c96b2b4140a164530f8f83cd0acrefactor(tekton/v1/tasks): refactor tidbx delivery task to use rotatingedittekton/v1/tasks/delivery/pingcap-notify-to-deliver-images-to-cloud-tidbx.yamlgithttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply