Started by GitHub push by ti-chi-bot[bot]00335513355169656696561.0051535153144043334e7d143b9719b842403c18bde95b5001632243334e7d143b9719b842403c18bde95b50016322origin/main43334e7d143b9719b842403c18bde95b5001632243334e7d143b9719b842403c18bde95b50016322origin/main43334e7d143b9719b842403c18bde95b5001632243334e7d143b9719b842403c18bde95b50016322origin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#14406965654520seed #14401440falsefalse14403320457SUCCESS1772183837774https://do.pingcap.net/jenkins/job/seed/1440/default-435txlibraries/tipipeline/vars/pod_label.groovy43334e7d143b9719b842403c18bde95b500163221772183795000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comci(lib): inject CI annotations by rewriting pod template (#4193) Background yamlFile + yaml overlay does not work reliably in our Jenkins Declarative setup. Even with yamlMergeStrategy, the annotation snippet is ignored, so CI annotations never make it into the final Pod. What this PR does Update withCiLabels to read the pod template (via readTrusted), merge CI annotations, and return a full YAML. Pipelines can then use: yaml pod_label.withCiLabels(POD_TEMPLATE_FILE, REFS) 2026-02-27 09:16:35 +000043334e7d143b9719b842403c18bde95b50016322ci(lib): inject CI annotations by rewriting pod template (#4193)editlibraries/tipipeline/vars/pod_label.groovygithttps://do.pingcap.net/jenkins/user/noreplynoreply