Started by GitHub push by ti-chi-bot[bot]00221752217561227612271.02729027290088517511451141445fff7ed0fb2477987e568dbce8a9d9dbf52723cd7fff7ed0fb2477987e568dbce8a9d9dbf52723cd7origin/mainfff7ed0fb2477987e568dbce8a9d9dbf52723cd7fff7ed0fb2477987e568dbce8a9d9dbf52723cd7origin/mainfff7ed0fb2477987e568dbce8a9d9dbf52723cd7fff7ed0fb2477987e568dbce8a9d9dbf52723cd7origin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1445/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1445/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1445/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1445/testsfalse#14456122744063seed #14451445falsefalse14453329701SUCCESS1772263439215https://do.pingcap.net/jenkins/job/seed/1445/default-j9vgl- pipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_light_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_heavy_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_light_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_heavy_next_gen/pipeline.groovypipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_heavy_next_gen/pipeline.groovyfff7ed0fb2477987e568dbce8a9d9dbf52723cd71772263406000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comci(pipelines): use pod_label helper for ticdc next-gen jobs (#4190)
What
Switch ticdc next‑gen Jenkins pipelines to use
[pod_label.withCiLabels(...)](app://-/index.html?hostId=local#) for pod
templates.
Why
Ensure CI pods carry minimal annotations (job, refs JSON, trigger user)
so Kyverno can derive labels.
Keep pipeline changes minimal and centralized via shared lib.
Notes
Declarative pipelines now use [yaml
pod_label.withCiLabels(...)](app://-/index.html?hostId=local#).
No label logic in Jenkins; Kyverno handles author/org/repo/env parsing.
2026-02-28 07:23:26 +0000fff7ed0fb2477987e568dbce8a9d9dbf52723cd7ci(pipelines): use pod_label helper for ticdc next-gen jobs (#4190)editpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_light_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_light_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_heavy_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_heavy_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_heavy_next_gen/pipeline.groovyeditpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy_next_gen/pipeline.groovy
githttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply