-
Notifications
You must be signed in to change notification settings - Fork 106
FAQ
This document provides answers to common questions about our CI/CD infrastructure, development processes, and community guidelines.
The PR's CI context display "Waiting for status to be reported" means that the PR is waiting for the CI to report the status. Please check if the PR has label needs-ok-to-test, if exists, please try to ask reviewer of the ORG to comment ok-to-test to trigger a new CI build. if the PR has no label needs-ok-to-test, but CI context still display "Waiting for status to be reported", please ask it in Ask EE group.
Follow these steps:
- Prepare your
tidb's PR. then prepare atidb-testPR to modify the mysql test cases. - Please comment '/hold' on your
tidb-test's PR. - In your tidb's PR, please specify the tidb-test's PR number in PR description. For example:
staistics: fix load stats from old version json | tidb-test=pr/2114 - At this time, triggering the mysql-test pipeline in your
tidbPR will use the test code from the specified tidb-test PR for testing. - After your
tidb's PR is merged, yourtidb-test's PR will be merged automatically by the ti-chi-bot.
Please ensure the base branch of your tidb-test's PR is the same as your tidb's PR. For example, if your tidb's PR is targeting master, your tidb-test's PR should targeting master. Only the base branch is same, the tidb-test's PR will be merged automatically after your tidb's PR is merged.
You can check the status of your PR's ci pipeline by clicking the "Details" link in the PR's ci context. For the new github PR merge experience UI, just click the ci checks context, you can see the link url of the ci check.
For tidb & tiflow & pd these repos have already supported batch merging, and there may be multiple PRs merged together. In this case, please wait patiently. You can check the progress of the merge queue through the prow tide dashboard https://prow.tidb.net/tide
Please upload the bazel dependencies in a internal machine.
tiprow is the optional self-test bot acted on pingcap/tidb repo, it's maintained by hawkingrei. It will not affect the merging for pull request(CI checks created by tiprow will not affect the merging).
Please comment /close or /reopen in the PR or Issue.
For PRs submitted by external contributors, the CI will not be triggered automatically. Please ask the reviewer to comment /ok-to-test to trigger the CI.
Please comment /hold or /unhold in the PR.
Please visit https://prow.tidb.net/command-help to find available commands.
Please chat with bot EE ChatOps in Lark IM(FeiShu).
For example: @EE ChatOps /cherry-pick-invite https://github.com/pingcap/tiflow/pull/10813 <your_github_id>
The "Merge is forbidden" tide status is expected behavior for HotFix branches. Once all CI checks pass, the bot will proceed with merging the PR automatically.
lgtm label is counted through voting; if two people give an LGTM, the PR will have the LGTM label. However, approval is determined based on the scope of changes in the modified files of the PR. If a PR modifies code across multiple modules, it will require approvals from all OWNERS of those changed modules before receiving the approved label.
- In order to trigger a recheck on an existing pull request you may need to push a new commit.
- If you have already pushed a new commit, you can try close and reopen the pull request.
- Check the url or the CLA status. It uses a public CLA service when the url is not "cla.pingcap.net"
- Open https://cla.pingcap.net/, "recheck" the PR of your repository by pushing the "Recheck PRs" button.
- If you can't find the repo which needs to
Recheck PRS, Please try to reopen the PR to resolve it.
Note: This FAQ is a living document and will be updated regularly