[release-4.14] OCPBUGS-20439: Rename manifest for Build CRD

[adambkaplan]

Marking the Build CRD as associated with the "Build" capability and "owned" by openshift-controller-manager-operator. This means that its CRD manifest will be included in the ocm-o image, with the right annotations to mark it as part of the "Build" capability.

This picks in updates from #1618 that were added after #1617 was merged.

[openshift-ci-robot]

@adambkaplan: This pull request references Jira Issue OCPBUGS-20164, which is invalid:

• expected the bug to target the "4.14.0" version, but it targets "4.15.0" instead
• expected Jira Issue OCPBUGS-20164 to depend on a bug targeting a version in 4.15.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Marking the Build CRD as associated with the "Build" capability and "owned" by openshift-controller-manager-operator. This means that its CRD manifest will be included in the ocm-o image, with the right annotations to mark it as part of the "Build" capability.

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.

[openshift-ci]

Hello @adambkaplan! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[openshift-ci-robot]

@adambkaplan: This pull request references Jira Issue OCPBUGS-20439, which is invalid:

• expected dependent Jira Issue OCPBUGS-20164 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Marking the Build CRD as associated with the "Build" capability and "owned" by openshift-controller-manager-operator. This means that its CRD manifest will be included in the ocm-o image, with the right annotations to mark it as part of the "Build" capability.

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.

[bparees]

/approve
/lgtm

[bparees]

/override ci/prow/verify-crd-schema

[openshift-ci]

@bparees: Overrode contexts on behalf of bparees: ci/prow/verify-crd-schema

Details

In response to this:

/override ci/prow/verify-crd-schema

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan, bparees

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:

• OWNERS [bparees]

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

[openshift-ci]

@adambkaplan: The following test 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/verify-crd-schema	b00fc53	link	true	/test verify-crd-schema

Full PR test history. Your PR dashboard.

Details

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-ci-robot]

@adambkaplan: Jira Issue OCPBUGS-20439: Some pull requests linked via external trackers have merged:

• openshift/api#1617

The following pull requests linked via external trackers have not merged:

• openshift/cluster-config-operator#363 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-20439 has not been moved to the MODIFIED state.

Details

In response to this:

Marking the Build CRD as associated with the "Build" capability and "owned" by openshift-controller-manager-operator. This means that its CRD manifest will be included in the ocm-o image, with the right annotations to mark it as part of the "Build" capability.

This picks in updates from #1618 that were added after #1617 was merged.

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.

[openshift-merge-robot]

Fix included in accepted release 4.14.0-0.nightly-2023-10-13-032002

[openshift-merge-robot]

Fix included in accepted release 4.14.0-0.nightly-2023-10-13-073537

[openshift-merge-robot]

Fix included in accepted release 4.15.0-0.nightly-2023-10-17-065657