Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00158951589544581445811.00705870581439c325140b2d5df00e5bf874d509789c4083ad2ffec325140b2d5df00e5bf874d509789c4083ad2ffeorigin/mainc325140b2d5df00e5bf874d509789c4083ad2ffec325140b2d5df00e5bf874d509789c4083ad2ffeorigin/mainc325140b2d5df00e5bf874d509789c4083ad2ffec325140b2d5df00e5bf874d509789c4083ad2ffeorigin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#14394458183303seed #14391439falsefalse14393316490SUCCESS1772165297412https://do.pingcap.net/jenkins/job/seed/1439/default-f2m0p- tekton/v1/triggers/triggers/env-gcp/_/git-create-tag-build-ng.yamltekton/v1/triggers/triggers/env-gcp/pingcap/tiproxy/git-create-tag.yamltekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-ng.yamltekton/v1/triggers/triggers/env-gcp/pingcap/tiproxy/git-push.yamlc325140b2d5df00e5bf874d509789c4083ad2ffe1772165270000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comcd(tekton/v1): update gcp triggers for next-gen (#4191)
remove tiproxy from generic gcp triggers and set profile to `next-gen`
by default. add release-nextgen and feature/tidb-zero branch matching
for push triggers and drop tiproxy-specific resource-config from the
shared mappings.
add pingcap/tiproxy-specific triggers: expand tag filter to accept
alpha/beta and nextgen tag formats and allow release-nextgen branch
pushes.
2026-02-27 04:07:50 +0000c325140b2d5df00e5bf874d509789c4083ad2ffecd(tekton/v1): update gcp triggers for next-gen (#4191)edittekton/v1/triggers/triggers/env-gcp/_/git-create-tag-build-ng.yamledittekton/v1/triggers/triggers/env-gcp/pingcap/tiproxy/git-push.yamledittekton/v1/triggers/triggers/env-gcp/pingcap/tiproxy/git-create-tag.yamledittekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-ng.yaml
githttps://do.pingcap.net/jenkins/user/noreplynoreply