Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup ownership of libvirt code #1662

Merged
merged 1 commit into from Apr 27, 2019

Conversation

zeenix
Copy link
Contributor

@zeenix zeenix commented Apr 23, 2019

This is to give ownership of libvirt backend of Installer to CRC team. For now I've only added two members from CRC team (myself and Praveen). I also added two members of Installer team who seem to have been the most active devs developing the relevant code.

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 23, 2019
OWNERS_ALIASES Show resolved Hide resolved
@abhinavdahiya
Copy link
Contributor

@zeenix Thanks for helping maintain the libvirt platform.

pkg/types/libvirt is public facing API for installer, its great that CRC team can help review that, but approve rights in that package will not be possible for now.

@zeenix
Copy link
Contributor Author

zeenix commented Apr 23, 2019

pkg/types/libvirt is public facing API for installer, its great that CRC team can help review that, but approve rights in that package will not be possible for now.

OK. I'll remove approvers from that one.

OWNERS_ALIASES Outdated Show resolved Hide resolved
@wking
Copy link
Member

wking commented Apr 23, 2019

pkg/types/libvirt is public facing API for installer, its great that CRC team can help review that, but approve rights in that package will not be possible for now.

OK. I'll remove approvers from that one.

Can you write this up in your commit message? Currently I could see some future dev looking at the commit and thinking the libvirt-reviewers omission there was a typo.

@abhinavdahiya
Copy link
Contributor

/test e2e-metal
/test e2e-vsphere

@abhinavdahiya
Copy link
Contributor

/test e2e-metal

This is to give ownership of libvirt backend of Installer to CRC team. For
now I've only added two members from CRC team (myself and Praveen). I also
added two members of Installer team who seem to have been the most active
devs developing the relevant code.

We don't add `libvirt-approvers` for `pkg/types/libvirt`. For reasons:

openshift#1662 (comment)
@zeenix
Copy link
Contributor Author

zeenix commented Apr 24, 2019

Can you write this up in your commit message?

@wking Done.

@wking
Copy link
Member

wking commented Apr 24, 2019

360b578 looks good to me, but I'll wait for @abhinavdahiya to sign off on it too.

@abhinavdahiya
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 24, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, zeenix

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:

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 24, 2019
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

6 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@abhinavdahiya
Copy link
Contributor

/test e2e-metal

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@abhinavdahiya
Copy link
Contributor

/test e2e-metal

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

5 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 27, 2019

@zeenix: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-vsphere fb590f5 link /test e2e-vsphere

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants