Skip to content
Success

Changes

Summary

  1. ci(pipelines): use pod_label helper for ticdc next-gen jobs (#4190) (commit: fff7ed0) (details)
Commit fff7ed0fb2477987e568dbce8a9d9dbf52723cd7 by noreply
ci(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.
(commit: fff7ed0)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_heavy_next_gen/pipeline.groovy (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_heavy_next_gen/pipeline.groovy (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light_next_gen/pipeline.groovy (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_light_next_gen/pipeline.groovy (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy_next_gen/pipeline.groovy (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pipeline.groovy (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_heavy_next_gen/pipeline.groovy (diff)
The file was modifiedpipelines/pingcap/ticdc/latest/pull_cdc_pulsar_integration_light_next_gen/pipeline.groovy (diff)