Skip to content

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Jan 29, 2026

This is manual cherrypick from #6149 PR

Description

Release Testing does not need to build any RPM, bootc image or rpm-ostree commit because all of them are fetched from the AWS S3 cache.

Changes

  • When running a Release Testing CI job, ci_phase_iso_build.sh:
    • Skip build RPMs from source, build rpm-ostree commits and bootc images.
    • Extract container images from brew RPMs
      • Added new arg into build_images.sh and build_bootc_images.py to skip all builds and only run extract_container_images().
  • Added release layer info in the README files for bootc and rpm-ostree.
  • Moved rhel96-bootc-brew-nightly-with-optional.containerfile from group2 into group1 fro consistency.

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

openshift-ci-robot commented Jan 29, 2026

@agullon: This pull request references USHIFT-6534 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 task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

This is manual cherrypick from #6149 PR

Description

Release Testing does not need to build any RPM, bootc image or rpm-ostree commit because all of them are fetched from the AWS S3 cache.

Changes

  • When running a Release Testing CI job, ci_phase_iso_build.sh:
    • Skip build RPMs from source, build rpm-ostree commits and bootc images.
    • Extract container images from brew RPMs
      • Added new arg into build_images.sh and build_bootc_images.py to skip all builds and only run extract_container_images().
  • Added release layer info in the README files for bootc and rpm-ostree.
  • Moved rhel96-bootc-brew-nightly-with-optional.containerfile from group2 into group1 fro consistency.

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

openshift-ci bot commented Jan 29, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon

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 Jan 29, 2026
@agullon
Copy link
Contributor Author

agullon commented Jan 29, 2026

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 29, 2026

@agullon: 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-aws-tests-bootc-periodic-arm c808a32 link true /test e2e-aws-tests-bootc-periodic-arm
ci/prow/e2e-aws-tests c808a32 link true /test e2e-aws-tests
ci/prow/e2e-aws-tests-bootc c808a32 link true /test e2e-aws-tests-bootc
ci/prow/e2e-aws-tests-periodic-arm c808a32 link true /test e2e-aws-tests-periodic-arm
ci/prow/e2e-aws-tests-periodic c808a32 link true /test e2e-aws-tests-periodic
ci/prow/e2e-aws-tests-bootc-periodic c808a32 link true /test e2e-aws-tests-bootc-periodic
ci/prow/e2e-aws-tests-bootc-arm c808a32 link true /test e2e-aws-tests-bootc-arm
ci/prow/e2e-aws-tests-arm c808a32 link true /test e2e-aws-tests-arm

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

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants