feat: switch to use new pipeline trigger by prow in branch 7.5

[purelind]

Swtich to use new pipeline trigger by prow in tikv & tiflash branch release-7.5

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Based on the pull request title and description, the key changes are that this pull request switches to using a new pipeline trigger by prow in the release-7.5 branch for the tikv and tiflash repositories.

Looking at the diff, the changes made are mainly in the Jenkins pipeline configuration files for the tikv and tiflash repositories and in the config.py file for the tidb-dashboard repository. The changes add release-7.5 as a blacklisted target branch in the Jenkins pipeline configuration files, indicating that pull requests targeting that branch should not trigger the pipeline. The changes to config.py for the tidb-dashboard repository have been commented out, which seems to indicate that the changes are not yet complete.

One potential problem with this pull request is that there is no explanation provided for why the new pipeline trigger is being used or what benefits it brings. It would be helpful to have more context on why this change is being made and what impact it will have on the CI/CD process.

Another potential issue is the change made to config.py for the tidb-dashboard repository. The changes have been commented out, which could indicate that they are not yet complete or that they are being temporarily disabled. It is not clear what the intention is here, so more information is needed.

Overall, the changes made in this pull request seem to be relatively minor and straightforward. To improve the pull request, it would be helpful to provide more context on why the new pipeline trigger is being used and to clarify the intentions behind the changes to config.py for the tidb-dashboard repository.

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Based on the pull request, the change is to switch to a new pipeline trigger by prow in tikv & tiflash branch release-7.5. The diff shows the changes in the blackListTargetBranches for the ghprbBranch.

There are no obvious potential problems with this pull request, but it's important to ensure that the new pipeline trigger is fully tested and validated before merging.

One suggestion for improvement would be to update the pull request description with more details about the new pipeline trigger and any testing that has been done to validate it. This would provide more context for reviewers and make it easier to assess the impact of the change.

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Based on the PR title and description, the changes seem to be related to switching to a new pipeline trigger for the tikv and tiflash branches for release-7.5. Here are some potential issues and suggestions for fixing them:

1. In the tikv job, the blackListTargetBranches section is missing the release-7.5 branch, which means that it is not being excluded from the job. The same issue exists in the tiflash jobs. The suggested fix is to add ghprbBranch { branch('release-7.5') } to the blackListTargetBranches section for both jobs.

2. In the tikv job, the always_run, optional, and skip_report options are set to false, which means that the job will not run by default. The suggested fix is to set these options to true so that the job runs.

3. In the tikv job, the context field is set to wip/pull-unit-test, which seems incorrect. The suggested fix is to change it to pull-unit-test.

4. In the tikv job, the trigger and rerun_command fields seem to be incorrect. The suggested fix is to change them to "(?m)^/test (?:.*? )?pull-unit-test(?: .*?)?$" and "/test pull-unit-test", respectively.

Overall, the changes seem reasonable, but the issues identified above should be fixed before merging the PR.

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Key changes:

• This pull request updates the pipeline trigger in the release-7.5 branch for tikv and tiflash.
• It updates the blackListTargetBranches to prevent triggering pipelines in master and other release branches except release-7.5.
• It updates the prow-jobs configuration files for tiflash and tikv to use the new pipeline trigger in the release-7.5 branch.

Potential problems:

• It is not clear why the pipeline trigger needs to be changed specifically for the release-7.5 branch. This should be explained in the pull request description or in the commit messages.
• It is not clear if any testing or validation has been done on the new pipeline trigger before this pull request was submitted.

Fixing suggestions:

• The pull request description should be updated to clarify the reason for the pipeline trigger change.
• The commit messages should provide more details about the changes made and any testing or validation done.
• It would be helpful to add some testing or validation steps in the pull request description or in the Jenkinsfile to ensure that the new pipeline trigger is working as expected.

[purelind]

/hold

[purelind]

tiflash

## tikv

[purelind]

/cc @Lloyd-Pottiger @JaySon-Huang @zanmato1984 @glorv @zhangjinpeng1987

[ti-chi-bot]

@purelind: GitHub didn't allow me to request PR reviews from the following users: zhangjinpeng1987.

Note that only PingCAP-QE members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @Lloyd-Pottiger @JaySon-Huang @zanmato1984 @glorv @zhangjinpeng1987

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ti-chi-bot]

@glorv: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ti-chi-bot]

@Lloyd-Pottiger: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ti-chi-bot]

@zanmato1984: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[wuhuizuo]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: glorv, Lloyd-Pottiger, wuhuizuo, zanmato1984

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• jenkins/OWNERS [wuhuizuo]
• prow-jobs/OWNERS [wuhuizuo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[purelind]

/unhold