Started by GitHub push by ti-chi-bot[bot]00216562165694742947421.00991599151107a11ecef7fcb1fe98f4a973c85e349c8e7bb136d1a11ecef7fcb1fe98f4a973c85e349c8e7bb136d1origin/maina11ecef7fcb1fe98f4a973c85e349c8e7bb136d1a11ecef7fcb1fe98f4a973c85e349c8e7bb136d1origin/maina11ecef7fcb1fe98f4a973c85e349c8e7bb136d1a11ecef7fcb1fe98f4a973c85e349c8e7bb136d1origin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#11079474280415seed #11071107falsefalse11072251170SUCCESS1761215725507https://do.pingcap.net/jenkins/view/all/job/seed/1107/default-srmq0- pipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pipeline.groovya11ecef7fcb1fe98f4a973c85e349c8e7bb136d11761215689000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comUpdate pipeline to use separate pod templates for build and test stages (#3844)
This pull request updates the pod template file paths for the
`pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen`
pipeline.
The changes are as follows:
* Updated `POD_TEMPLATE_FILE` to point to `pod-test.yaml`.
* Updated `POD_TEMPLATE_FILE_BUILD` to point to `pod-build.yaml`.
This change is necessary to differentiate between pod configurations
used for testing and those used for building, allowing for more specific
and controlled resource allocation for each stage of the pipeline.
Signed-off-by: tenfyzhong <tenfy@tenfy.cn>
2025-10-23 10:34:49 +0000a11ecef7fcb1fe98f4a973c85e349c8e7bb136d1Update pipeline to use separate pod templates for build and test stageseditpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pipeline.groovy
githttps://do.pingcap.net/jenkins/user/noreplynoreply