Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00192451924546621466211.008438843814508c47148a13ed50d245856a44c91664cb3e2346ad8c47148a13ed50d245856a44c91664cb3e2346adorigin/main8c47148a13ed50d245856a44c91664cb3e2346ad8c47148a13ed50d245856a44c91664cb3e2346adorigin/main8c47148a13ed50d245856a44c91664cb3e2346ad8c47148a13ed50d245856a44c91664cb3e2346adorigin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#14504662150732seed #14501450falsefalse14503349236SUCCESS1772449768803https://do.pingcap.net/jenkins/job/seed/1450/default-9n808- jobs/pingcap/tidb/latest/periodics_integration_test.groovyprow-jobs/pingcap/tidb/latest-periodics.yaml8c47148a13ed50d245856a44c91664cb3e2346ad1772449736000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comMigrate Jenkins cron-triggered integration test to Prow periodic (#4264)
The `periodics_integration_test` job for `pingcap/tidb` (latest/master)
was self-scheduling via a Jenkins cron trigger (`0 * * * *`), bypassing
Prow and causing potential duplication with centrally-managed
scheduling.
## Changes
- **`prow-jobs/pingcap/tidb/latest-periodics.yaml`** — Added Prow
periodic entry for `pingcap/tidb/latest/periodics_integration_test`
using `agent: jenkins`, retaining the original hourly schedule:
```yaml
- name: pingcap/tidb/latest/periodics_integration_test
agent: jenkins
labels:
master: "0" # Jenkins master instance to run this job (0 = default
master)
decorate: false
cron: "0 * * * *" # every hour
extra_refs:
- org: pingcap
repo: tidb
base_ref: master
```
- **`jobs/pingcap/tidb/latest/periodics_integration_test.groovy`** —
Removed `pipelineTriggers { triggers { cron{ spec('0 * * * *') } } }`
block. The Jenkins job definition is retained so Prow can invoke it;
scheduling ownership now lives exclusively in Prow.
<!-- START COPILOT ORIGINAL PROMPT -->
<details>
<summary>Original prompt</summary>
>
> ----
>
> *This section details on the original issue you should resolve*
>
> <issue_title>Migrate Jenkins cron jobs to Prow periodic</issue_title>
> <issue_description>Identify Jenkins scheduled/periodic jobs and move
them to Prow periodic jobs to avoid multi-Jenkins duplication.
>
> Acceptance criteria:
> - Jenkins cron triggers removed or disabled
> - Equivalent Prow periodic jobs added
> - Schedule ownership documented
> </issue_description>
>
> <agent_instructions>the jenkins job defined in `jobs/`
folder.</agent_instructions>
>
> ## Comments on the Issue (you are @copilot in this section)
>
> <comments>
> </comments>
>
</details>
<!-- START COPILOT CODING AGENT SUFFIX -->
- Fixes PingCAP-QE/ci#4207
<!-- START COPILOT CODING AGENT TIPS -->
---
🔒 GitHub Advanced Security automatically protects Copilot coding agent
pull requests. You can protect all pull requests by enabling Advanced
Security for your repositories. [Learn more about Advanced
Security.](https://gh.io/cca-advanced-security)
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: wuhuizuo <2574558+wuhuizuo@users.noreply.github.com>
2026-03-02 11:08:56 +00008c47148a13ed50d245856a44c91664cb3e2346adMigrate Jenkins cron-triggered integration test to Prow periodic (#4264)editjobs/pingcap/tidb/latest/periodics_integration_test.groovyeditprow-jobs/pingcap/tidb/latest-periodics.yaml
githttps://do.pingcap.net/jenkins/user/noreplynoreply