Skip to content

[release-4.21] USHIFT-6534: Skip RPM and image builds for release testing CI jobs#6170

Merged
openshift-merge-bot[bot] merged 13 commits intoopenshift:release-4.21from
agullon:USHIFT-6534_421
Jan 31, 2026
Merged

[release-4.21] USHIFT-6534: Skip RPM and image builds for release testing CI jobs#6170
openshift-merge-bot[bot] merged 13 commits intoopenshift:release-4.21from
agullon:USHIFT-6534_421

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

@agullon
Copy link
Contributor Author

agullon commented Jan 30, 2026

/retest

@agullon
Copy link
Contributor Author

agullon commented Jan 30, 2026

/test e2e-aws-tests-bootc-release
/test e2e-aws-tests-release
/test e2e-aws-tests-bootc-release-arm
/test e2e-aws-tests-release-arm

@agullon
Copy link
Contributor Author

agullon commented Jan 30, 2026

/retest

1 similar comment
@agullon
Copy link
Contributor Author

agullon commented Jan 30, 2026

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2026

@agullon: all tests passed!

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.

@ggiguash
Copy link
Contributor

/lgtm
/verified by ci
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jan 31, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 31, 2026
@openshift-ci-robot
Copy link

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/lgtm
/verified by ci
/label backport-risk-assessed
/label jira/valid-bug

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 lgtm Indicates that a PR is ready to be merged. label Jan 31, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, ggiguash

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-merge-bot openshift-merge-bot bot merged commit 6f1b837 into openshift:release-4.21 Jan 31, 2026
20 checks passed
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants