origin
origin copied to clipboard
openshift
add some QE approvers/reviewers
Openshift QEs are encouraged to contribute test cases to the origin repo. To balance the PR review workloads, I add some reviewers and approvers who have rich experience with Golang.
As the distribution of the PRs based on the component, the PR review process for QE:
- The PR owner, teams, groups to review the PR and add
/lgtmlabel if the PR looks good. The reviewer should guarantee the case's quality. - The approvers add the
/approvelabel if it looks good. The approver should guarantee the case quality at a high level, such as, if it will break other cases.
cc: @xltian @chengzhang1016
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jianzhangbjz
To complete the pull request process, please assign bparees after the PR has been reviewed.
You can assign the PR to them by writing /assign @bparees in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
/uncc I don't feel like I have enough approval power here that I should be approving new approvers...
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
@jianzhangbjz: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-aws-single-node | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | false | /test e2e-aws-single-node |
| ci/prow/e2e-gcp-csi | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | false | /test e2e-gcp-csi |
| ci/prow/e2e-agnostic-cmd | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | false | /test e2e-agnostic-cmd |
| ci/prow/e2e-aws-ovn-serial | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | true | /test e2e-aws-ovn-serial |
| ci/prow/e2e-aws-ovn-fips | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | true | /test e2e-aws-ovn-fips |
| ci/prow/e2e-gcp-ovn | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | true | /test e2e-gcp-ovn |
Full PR test history. Your PR dashboard.
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. I understand the commands that are listed here.
@jianzhangbjz: PR needs rebase.
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.
@jianzhangbjz: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-aws-single-node | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | false | /test e2e-aws-single-node |
| ci/prow/e2e-gcp-csi | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | false | /test e2e-gcp-csi |
| ci/prow/e2e-agnostic-cmd | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | false | /test e2e-agnostic-cmd |
| ci/prow/e2e-aws-ovn-serial | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | true | /test e2e-aws-ovn-serial |
| ci/prow/e2e-aws-ovn-fips | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | true | /test e2e-aws-ovn-fips |
| ci/prow/e2e-gcp-ovn | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | true | /test e2e-gcp-ovn |
| ci/prow/unit | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | true | /test unit |
| ci/prow/e2e-aws-ovn-image-registry | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | true | /test e2e-aws-ovn-image-registry |
| ci/prow/e2e-gcp-ovn-builds | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | true | /test e2e-gcp-ovn-builds |
| ci/prow/e2e-gcp-ovn-image-ecosystem | 40a103b5ad9649c158b79780b1cb179c3668f4f8 | link | true | /test e2e-gcp-ovn-image-ecosystem |
Full PR test history. Your PR dashboard.
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. I understand the commands that are listed here.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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.