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

NO-JIRA: build only needed cmd in container image #329

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sanchezl
Copy link

No description provided.

@openshift-ci openshift-ci bot requested review from gnufied and jsafrane November 22, 2024 16:17
@jsafrane
Copy link
Contributor

jsafrane commented Dec 9, 2024

/retitle NO-JIRA: build only needed cmd in container image
/retest-required
/lgtm
/approve

This is not an user visible change
/label px-approved
/label docs-approved
/label qe-approved
CI should be enough to test this

@openshift-ci openshift-ci bot changed the title build only needed cmd in container image NO-JIRA: build only needed cmd in container image Dec 9, 2024
@openshift-ci openshift-ci bot added the px-approved Signifies that Product Support has signed off on this PR label Dec 9, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 9, 2024
@openshift-ci openshift-ci bot added the docs-approved Signifies that Docs has signed off on this PR label Dec 9, 2024
@openshift-ci-robot
Copy link

@sanchezl: This pull request explicitly references no jira issue.

In response to this:

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 openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Dec 9, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 9, 2024
Copy link
Contributor

openshift-ci bot commented Dec 9, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, sanchezl

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 9, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b8d4036 and 2 for PR HEAD 7f26187 in total

Copy link
Contributor

openshift-ci bot commented Dec 10, 2024

@sanchezl: 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-openstack 7f26187 link false /test e2e-openstack
ci/prow/okd-scos-e2e-aws-ovn 7f26187 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-azurestack-csi 7f26187 link false /test e2e-azurestack-csi
ci/prow/hypershift-e2e-openstack-csi-manila 7f26187 link true /test hypershift-e2e-openstack-csi-manila
ci/prow/hypershift-e2e-openstack-csi-cinder 7f26187 link true /test hypershift-e2e-openstack-csi-cinder

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.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b8d4036 and 2 for PR HEAD 7f26187 in total

@jsafrane
Copy link
Contributor

jsafrane commented Jan 2, 2025

/retest-required

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. docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants