Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00192451924542480424801.00503550351103e25da8b11c5f865ea77763d0693d9df2e05d20d2e25da8b11c5f865ea77763d0693d9df2e05d20d2origin/maine25da8b11c5f865ea77763d0693d9df2e05d20d2e25da8b11c5f865ea77763d0693d9df2e05d20d2origin/maine25da8b11c5f865ea77763d0693d9df2e05d20d2e25da8b11c5f865ea77763d0693d9df2e05d20d2origin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#11034248080415seed #11031103falsefalse11032244738SUCCESS1761185714918https://do.pingcap.net/jenkins/view/all/job/seed/1103/default-vv4w1tekton/v1/triggers/triggers/_/git-create-tag-build-ng.yamltekton/v1/triggers/triggers/_/git-push-branch-build-ng.yamltekton/v1/triggers/triggers/_/git-create-branch-ng.yamle25da8b11c5f865ea77763d0693d9df2e05d20d21761185686000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comchore(tekton/v1): add pingcap/tiproxy to Next-Gen build triggers (#3841) ## Overview This PR expands the build range for the `pingcap/tiproxy` repository to support Next-Gen branches and tags in the tekton/v1 pipeline system. ## Changes Added `pingcap/tiproxy` to three Next-Gen trigger configurations: ### 1. Branch Creation Trigger (`git-create-branch-ng.yaml`) - Triggers on `release-nextgen-*` branch creation (e.g., `release-nextgen-1`, `release-nextgen-10`) - Automatically bumps placeholder versions in README when new Next-Gen release branches are created ### 2. Branch Push/Build Trigger (`git-push-branch-build-ng.yaml`) - Triggers builds on pushes to `master` and `release-nextgen-*` branches - Build configuration: - Timeout: 20 minutes - Source workspace: 50Gi - CPU: 4 cores - Memory: 16Gi - **Profile: `release`** (tiproxy uses `release` profile; other repos use `next-gen`) ### 3. Tag Creation/Build Trigger (`git-create-tag-build-ng.yaml`) - Triggers builds on Next-Gen tag creation matching pattern: `vX.Y.Z-nextgen.YYMMDD.N` - Example: `v1.0.0-nextgen.202510.1`, `v8.5.0-nextgen.241022.3` - Uses same build configuration as branch builds - **Profile: `release`** (tiproxy uses `release` profile; other repos use `next-gen`) ## Resource Configuration The build resources are configured based on: - Similar-sized components (ticdc, pd) in the Next-Gen pipeline - Existing tiproxy configuration from tekton/v0 - Conservative allocation suitable for tiproxy's build requirements ## Profile Configuration A conditional profile overlay has been added to ensure `pingcap/tiproxy` builds with the `release` profile (consistent with its v0 configuration), while other repositories (ticdc, tidb, tiflash, pd, cloud-storage-engine) continue to use the `next-gen` profile. ## Testing - ✅ All modified YAML files validated for syntax correctness - ✅ Build patterns tested and verified against expected branch/tag formats - ✅ Profile assignment logic validated for correct profile selection per repository - ✅ CodeQL security analysis passed ## Impact This change enables the `pingcap/tiproxy` repository to participate in the Next-Gen build pipeline alongside other core PingCAP components, supporting the Next-Gen development and release workflow with the appropriate `release` profile. Fixes PingCAP-QE/ci#3839 <!-- START COPILOT CODING AGENT SUFFIX --> <details> <summary>Original prompt</summary> > > ---- > > *This section details on the original issue you should resolve* > > <issue_title>[Next-Gen] expend build range for `pingcap/tiproxy` repo: support `release-nextgen-*` branches and support `vX.Y.Z-nextgen-*` tags</issue_title> > <issue_description></issue_description> > > <agent_instructions>implement it on `tekton/v1` folder</agent_instructions> > > ## Comments on the Issue (you are @copilot in this section) > > <comments> > </comments> > </details> Fixes PingCAP-QE/ci#3839 <!-- START COPILOT CODING AGENT TIPS --> --- ✨ Let Copilot coding agent [set things up for you](https://github.com/PingCAP-QE/ci/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: wuhuizuo <2574558+wuhuizuo@users.noreply.github.com> 2025-10-23 02:14:46 +0000e25da8b11c5f865ea77763d0693d9df2e05d20d2chore(tekton/v1): add pingcap/tiproxy to Next-Gen build triggers (#3841)edittekton/v1/triggers/triggers/_/git-create-tag-build-ng.yamledittekton/v1/triggers/triggers/_/git-push-branch-build-ng.yamledittekton/v1/triggers/triggers/_/git-create-branch-ng.yamlgithttps://do.pingcap.net/jenkins/user/noreplynoreply