Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00302193021951597515971.005047504711927f0017b6fb12d92c62017c8d42730434235222af7f0017b6fb12d92c62017c8d42730434235222aforigin/main7f0017b6fb12d92c62017c8d42730434235222af7f0017b6fb12d92c62017c8d42730434235222aforigin/main7f0017b6fb12d92c62017c8d42730434235222af7f0017b6fb12d92c62017c8d42730434235222aforigin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#11925159780415seed #11921192falsefalse11922554855SUCCESS1764584869778https://do.pingcap.net/jenkins/view/all/job/seed/1192/default-w5bw0tekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-ng.yamltekton/v1/triggers/triggers/env-gcp/_/git-create-tag-build-ng.yaml7f0017b6fb12d92c62017c8d42730434235222af1764584831000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comrefactor(tekton/v1): change registry to tidbx in Tekton triggers for tidbx builds (#3944) This pull request updates the registry used for image builds in the Tekton pipeline configuration files for the GCP environment. The registry is changed from `hub` to `tidbx` to ensure images are pushed to the correct location. Configuration updates: * Updated the `registry` value in `git-create-tag-build-ng.yaml` to use `us-docker.pkg.dev/pingcap-testing-account/tidbx` instead of `hub`. * Updated the `registry` value in `git-push-branch-build-ng.yaml` to use `us-docker.pkg.dev/pingcap-testing-account/tidbx` instead of `hub`. 2025-12-01 10:27:11 +00007f0017b6fb12d92c62017c8d42730434235222afrefactor(tekton/v1): change registry to tidbx in Tekton triggers foredittekton/v1/triggers/triggers/env-gcp/_/git-push-branch-build-ng.yamledittekton/v1/triggers/triggers/env-gcp/_/git-create-tag-build-ng.yamlgithttps://do.pingcap.net/jenkins/user/noreplynoreply