Skip to content

ART-14008: add agent-installer-ui.yml#7754

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift-eng:openshift-4.21from
Ximinhan:openshift-4.21
Sep 29, 2025
Merged

ART-14008: add agent-installer-ui.yml#7754
openshift-merge-bot[bot] merged 2 commits intoopenshift-eng:openshift-4.21from
Ximinhan:openshift-4.21

Conversation

@Ximinhan
Copy link
Contributor

@Ximinhan Ximinhan commented Sep 25, 2025

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 25, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 25, 2025

@Ximinhan: This pull request references ART-14008 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.21.0" version, but no target version was set.

Details

In response to this:

ref https://issues.redhat.com/browse/ART-14008

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-robot
Copy link

openshift-ci-robot commented Sep 26, 2025

@Ximinhan: This pull request references ART-14008 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.21.0" version, but no target version was set.

Details

In response to this:

ref https://issues.redhat.com/browse/ART-14008
test build: https://konflux-ui.apps.kflux-ocp-p01.7ayg.p1.openshiftapps.com/ns/ocp-art-tenant/applications/openshift-4-21/pipelineruns/ose-4-21-agent-installer-ui-jjrtk

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.

@ashwindasr
Copy link
Contributor

/retest

x86_64: linux-d160-c4xlarge/amd64
aarch64: linux-d160-c4xlarge/arm64
cachi2:
artifact_lockfile:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the build should work without the Current-IT-Root-CAs.pem being explicitly added. And not sure if we need the artifact_lockfile since the build is non-hermetic

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

Copy link
Contributor

@joepvd joepvd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 29, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joepvd

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 29, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 4fbe3fa into openshift-eng:openshift-4.21 Sep 29, 2025
3 checks passed
@Ximinhan
Copy link
Contributor Author

/cherrypick openshift-4.20

@openshift-cherrypick-robot

@Ximinhan: new pull request created: #7850

Details

In response to this:

/cherrypick openshift-4.20

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.

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. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants