Started by GitHub push by ti-chi-bot[bot]00253162531645800458001.0081998199191e2be149558d2534398efa23178f911e3fee17516e2be149558d2534398efa23178f911e3fee17516origin/maine2be149558d2534398efa23178f911e3fee17516e2be149558d2534398efa23178f911e3fee17516origin/maine2be149558d2534398efa23178f911e3fee17516e2be149558d2534398efa23178f911e3fee17516origin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#1914580080415seed #191191falsefalse191293805SUCCESS1712666488860https://do.pingcap.net/jenkins/view/all/job/seed/191/default-2tpwv- prow-jobs/pingcap-tidb-latest-presubmits.yamle2be149558d2534398efa23178f911e3fee175161712666451000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comfeat: br ci support run_if_changed (#2885)
The br & lightning pipeline supports triggering based on conditions. If
code changes are detected in the corresponding directory, the
corresponding test pipeline will be triggered. Block PR merging if the
test pipeline execution fails.
It should be noted that because prow does not support configuring these
two parameters at the same time (`run_if_changed` and
`skip_if_only_changed`), after applying this change. If there are
changes in pure document categories for br & lightning, it will also
trigger the test pipeline.
2024-04-09 12:40:51 +0000e2be149558d2534398efa23178f911e3fee17516feat: br ci support run_if_changed (#2885)editprow-jobs/pingcap-tidb-latest-presubmits.yaml
githttps://do.pingcap.net/jenkins/user/noreplynoreply