OPRUN-3742: add operator-framework/operator-controller tide config

[grokspawn]

Solves

• (RH) prow config should be used to enforce review/approver status by label operator-framework/community#108
• (RH) no test jobs should need to be configured operator-framework/community#109
• (RH) repos should require 2 labels: approve / lgtm to merge operator-framework/community#110
• (RH) prow should accept review approval as an lgtm (or approve?) operator-framework/community#111
• (RH) branch protection needs to be turned on for the master/main branches in prow so that it requires pass of the same CI jobs operator-framework/community#114

Adds prow/tide config to the repo so we can support separate reviewer/approver tiers.

Apologies for the churn. I initially attempted to include ci-operator in prow, but rolled it back. We'll handle this separately/later if we want to pursue it further.

[openshift-ci-robot]

@grokspawn: This pull request references OPRUN-3742 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

Solves

• (RH) prow config should be used to enforce review/approver status by label operator-framework/community#108
• (RH) no test jobs should need to be configured operator-framework/community#109
• (RH) repos should require 2 labels: approve / lgtm to merge operator-framework/community#110
• (RH) prow should accept review approval as an lgtm (or approve?) operator-framework/community#111
• (RH) branch protection needs to be turned on for the master/main branches in prow so that it requires pass of the same CI jobs operator-framework/community#114

Adds prow/tide config to the repo so we can support separate reviewer/approver tiers.

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 openshift-eng/jira-lifecycle-plugin repository.

[grokspawn]

/pj-rehearse auto-ack

[openshift-ci-robot]

@grokspawn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[grokspawn]

/pj-rehearse pull-ci-operator-framework-operator-controller-main-build

[openshift-ci-robot]

@grokspawn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[grokspawn]

/pj-rehearse pull-ci-operator-framework-operator-controller-main-build

[openshift-ci-robot]

@grokspawn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[grokspawn]

/pj-rehearse pull-ci-operator-framework-operator-controller-main-build

[openshift-ci-robot]

@grokspawn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[grokspawn]

/pj-rehearse skip

[openshift-ci-robot]

@grokspawn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[grokspawn]

/pj-rehearse pull-ci-operator-framework-operator-controller-main-build

[openshift-ci-robot]

@grokspawn: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci-robot]

@grokspawn: This pull request references OPRUN-3742 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

Solves

• (RH) prow config should be used to enforce review/approver status by label operator-framework/community#108
• (RH) no test jobs should need to be configured operator-framework/community#109
• (RH) repos should require 2 labels: approve / lgtm to merge operator-framework/community#110
• (RH) prow should accept review approval as an lgtm (or approve?) operator-framework/community#111
• (RH) branch protection needs to be turned on for the master/main branches in prow so that it requires pass of the same CI jobs operator-framework/community#114

Adds prow/tide config to the repo so we can support separate reviewer/approver tiers.

Apologies for the churn. I initially attempted to include ci-operator in prow, but rolled it back. We'll handle this separately/later if we want to pursue it further.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@grokspawn: 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/rehearse/operator-framework/operator-controller/main/unit	9c4280f	link	unknown	/pj-rehearse pull-ci-operator-framework-operator-controller-main-unit
ci/rehearse/operator-framework/operator-controller/main/e2e-upgrade	9c4280f	link	unknown	/pj-rehearse pull-ci-operator-framework-operator-controller-main-e2e-upgrade
ci/rehearse/operator-framework/operator-controller/main/e2e	9c4280f	link	unknown	/pj-rehearse pull-ci-operator-framework-operator-controller-main-e2e
ci/rehearse/operator-framework/operator-controller/main/verify	9c4280f	link	unknown	/pj-rehearse pull-ci-operator-framework-operator-controller-main-verify
ci/rehearse/operator-framework/operator-controller/main/build	e582490	link	unknown	/pj-rehearse pull-ci-operator-framework-operator-controller-main-build

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-sigs/prow repository. I understand the commands that are listed here.

[grokspawn]

now rebased to master/HEAD

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@grokspawn: no rehearsable tests are affected by this change

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@grokspawn: no rehearsable tests are affected by this change

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[tmshort]

Do we have jira integration?

[grokspawn]

That plugin is not enabled here.
I didn't figure that we needed to ignore/omit the label, since these are "do not merge if present" label lists.

[dtfranz]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dtfranz, grokspawn

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]

@grokspawn: Updated the following 2 configmaps:

• plugins configmap in namespace ci at cluster app.ci using the following files:
  • key core-services-prow-02_config-operator-framework-operator-controller-_pluginconfig.yaml using file core-services/prow/02_config/operator-framework/operator-controller/_pluginconfig.yaml
• config configmap in namespace ci at cluster app.ci using the following files:
  • key core-services-prow-02_config-operator-framework-operator-controller-_prowconfig.yaml using file core-services/prow/02_config/operator-framework/operator-controller/_prowconfig.yaml

In response to this:

Solves

• (RH) prow config should be used to enforce review/approver status by label operator-framework/community#108
• (RH) no test jobs should need to be configured operator-framework/community#109
• (RH) repos should require 2 labels: approve / lgtm to merge operator-framework/community#110
• (RH) prow should accept review approval as an lgtm (or approve?) operator-framework/community#111
• (RH) branch protection needs to be turned on for the master/main branches in prow so that it requires pass of the same CI jobs operator-framework/community#114

Adds prow/tide config to the repo so we can support separate reviewer/approver tiers.

Apologies for the churn. I initially attempted to include ci-operator in prow, but rolled it back. We'll handle this separately/later if we want to pursue it further.

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-sigs/prow repository.