Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00305053050543612436121.0379123791208152474067406180175091264ca311a2e2c77ade5f532de707b9d0bb075091264ca311a2e2c77ade5f532de707b9d0bb0origin/main75091264ca311a2e2c77ade5f532de707b9d0bb075091264ca311a2e2c77ade5f532de707b9d0bb0origin/main75091264ca311a2e2c77ade5f532de707b9d0bb075091264ca311a2e2c77ade5f532de707b9d0bb0origin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1801/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1801/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1801/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1801/testsfalse#18014361249176seed #18011801falsefalse18013694168SUCCESS1782121914621https://do.pingcap.net/jenkins/job/seed/1801/default-jc777tekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-enterprise.yamltekton/v1/triggers/bindings/kustomization.yamltekton/v1/triggers/bindings/gcp-dev-build-params.yamltekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-pr.yamltekton/v1/triggers/triggers/env-gcp/kustomization.yamltekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-community-linux.yamltekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-pr-single-platform.yamltekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-branch-push-single-platform.yamltekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-tag-create.yamltekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-tag-create-single-platform.yamltekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-branch-push.yaml75091264ca311a2e2c77ade5f532de707b9d0bb01782121872000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comci(tekton): add fake-github triggers to env-gcp (#4714) ## Summary - add the `fake-github` trigger set under `tekton/v1/triggers/triggers/env-gcp/_/fake-github` - register the six new trigger manifests in the `env-gcp` Tekton kustomization - keep the `env-gcp` wiring aligned with the existing `env-prod2` fake-github trigger implementation ## Validation - `kubectl kustomize tekton/v1/triggers/triggers/env-gcp >/dev/null` - `kubectl kustomize tekton/v1/triggers/templates >/dev/null` ## Notes - `.ci/update-tekton-kustomizations.sh` was run; it reports the checked-in kustomization diff while the new resources are uncommitted, but the resulting resource ordering is aligned. - `pre-commit` is not installed in this environment, so hook-based checks were not run locally. 2026-06-22 09:51:12 +000075091264ca311a2e2c77ade5f532de707b9d0bb0ci(tekton): add fake-github triggers to env-gcp (#4714)edittekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-community-linux.yamladdtekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-branch-push-single-platform.yamladdtekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-pr-single-platform.yamladdtekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-branch-push.yamledittekton/v1/triggers/bindings/kustomization.yamledittekton/v1/triggers/triggers/env-gcp/kustomization.yamladdtekton/v1/triggers/bindings/gcp-dev-build-params.yamledittekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-enterprise.yamladdtekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-tag-create.yamladdtekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-pr.yamladdtekton/v1/triggers/triggers/env-gcp/_/fake-github/fake-github-tag-create-single-platform.yamlgithttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply