Skip to content

Conversation

@wking
Copy link
Member

@wking wking commented Jun 17, 2020

Step-registry CI currently requires each directory to contain an OWNERS file (ci/prow/owners). Often, those OWNERS sets are the same as the parent-directory's OWNERS file. To ease maintenance, we can use symlinks to ../OWNERS to explicitly say "this is the same set", as we started to do in 0f27f00 (#9612). This commit adds a script to automate that deduping, and also commits the state generated by:

$ hack/dedup-owners.sh ci-operator/step-registry

Step-registry CI currently requires each directory to contain an
OWNERS file (ci/prow/owners).  Often, those OWNERS sets are the same
as the parent-directory's OWNERS file.  To ease maintenance, we can
use symlinks to ../OWNERS to explicitly say "this is the same set", as
we started to do in 0f27f00 (ci-operator/step-registry/openshift:
Push e2e flavors under e2e/, 2020-06-10, openshift#9612).  This commit adds a
script to automate that deduping, and also commits the state generated
by:

  $ hack/dedup-owners.sh ci-operator/step-registry
@wking
Copy link
Member Author

wking commented Jun 17, 2020

/assign @hongkailiu

All green, and Blunderbuss suggested you :).

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 18, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongkailiu, wking

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

The pull request process is described here

Details 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 Jun 18, 2020
@openshift-merge-robot openshift-merge-robot merged commit 013c698 into openshift:master Jun 18, 2020
@openshift-ci-robot
Copy link
Contributor

@wking: Updated the following 2 configmaps:

  • step-registry configmap in namespace ci at cluster api.ci using the following files:
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/conf/compact/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/conf/dualstack/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/conf/ipv4/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/gather/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/e2e/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/e2e/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/packet/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/packet/setup/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/packet/teardown/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/gather/audit-logs/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/gather/extra/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/gather/loki/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/gather/must-gather/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/gather/network/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/aws/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/aws/ovn/hybrid/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/aws/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/aws/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/aws/pre/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/azure/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/azure/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/azure/pre/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/aws/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/aws/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/azure/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/gcp/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/vsphere/dns/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/vsphere/vips/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/deprovision/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/deprovision/deprovision/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/deprovision/vsphere/dns/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/deprovision/vsphere/vips/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/gcp/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/gcp/pre/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/install/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/install/install/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/install/rbac/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/install/vsphere/registry/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/vsphere/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/vsphere/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/aws/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/aws/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/azure/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/upi/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/optional-operators/cvp-common/aws/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/optional-operators/cvp-common/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/optional-operators/subscribe/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/conf/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/deprovision/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/install/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/windows/e2e/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/windows/e2e/operator/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/windows/e2e/operator/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/windows/e2e/playbook/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/windows/e2e/playbook/test/OWNERS
  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/conf/compact/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/conf/dualstack/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/conf/ipv4/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/gather/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/e2e/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/e2e/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/packet/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/packet/setup/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/packet/teardown/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/gather/audit-logs/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/gather/extra/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/gather/loki/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/gather/must-gather/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/gather/network/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/aws/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/aws/ovn/hybrid/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/aws/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/aws/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/aws/pre/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/azure/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/azure/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/azure/pre/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/aws/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/aws/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/azure/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/gcp/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/vsphere/dns/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/vsphere/vips/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/deprovision/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/deprovision/deprovision/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/deprovision/vsphere/dns/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/deprovision/vsphere/vips/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/gcp/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/gcp/pre/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/install/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/install/install/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/install/rbac/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/install/vsphere/registry/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/vsphere/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/vsphere/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/aws/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/aws/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/azure/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/sharednetwork/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/upi/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/optional-operators/cvp-common/aws/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/optional-operators/cvp-common/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/optional-operators/subscribe/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/conf/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/deprovision/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/install/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/windows/e2e/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/windows/e2e/operator/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/windows/e2e/operator/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/windows/e2e/playbook/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/windows/e2e/playbook/test/OWNERS
Details

In response to this:

Step-registry CI currently requires each directory to contain an OWNERS file (ci/prow/owners). Often, those OWNERS sets are the same as the parent-directory's OWNERS file. To ease maintenance, we can use symlinks to ../OWNERS to explicitly say "this is the same set", as we started to do in 0f27f00 (#9612). This commit adds a script to automate that deduping, and also commits the state generated by:

$ hack/dedup-owners.sh ci-operator/step-registry

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.

@wking wking deleted the step-owners-dedup branch June 18, 2020 12:07
wking added a commit to wking/openshift-release that referenced this pull request Oct 14, 2020
Like 0a90079 (ci-operator/step-registry: Dedup OWNERS with
symlinks, 2020-06-17, openshift#9739), picking up all the dups that have crept
in since then.  Generated with:

  $ hack/dedup-owners.sh ci-operator/step-registry
wking added a commit to wking/openshift-release that referenced this pull request Jan 25, 2022
Like 0a90079 (ci-operator/step-registry: Dedup OWNERS with
symlinks, 2020-06-17, openshift#9739), picking up all the dups that have crept
in since the most recent round, possibly e168265
(assisted-installer: Dedup OWNERS files using hack/dedup-owners.sh,
2021-07-06, openshift#19931).  Generated with:

  $ hack/dedup-owners.sh ci-operator/step-registry
wking added a commit to wking/openshift-release that referenced this pull request Apr 29, 2022
Like 0a90079 (ci-operator/step-registry: Dedup OWNERS with
symlinks, 2020-06-17, openshift#9739) and 9c1d14a
(ci-operator/step-registry: Dedup OWNERS with symlinks again,
2022-01-24, openshift#25574), picking up all the dups that have crept in since
the most recent round, possibly 9c1d14a.  Generated with:

  $ hack/dedup-owners.sh ci-operator/step-registry
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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants