Skip to content

[release-4.13] NO-JIRA: enable multi-architecture yarn builds#16423

Open
logonoff wants to merge 1 commit intoopenshift:release-4.13from
logonoff:yarn-4.13
Open

[release-4.13] NO-JIRA: enable multi-architecture yarn builds#16423
logonoff wants to merge 1 commit intoopenshift:release-4.13from
logonoff:yarn-4.13

Conversation

@logonoff
Copy link
Copy Markdown
Member

@logonoff logonoff commented May 8, 2026

This is an automated cherry-pick of #16228

@lgarciaaco @logonoff
build(frontend): enable multi-architecture yarn builds
6fec134 
Convert Dockerfile to use hermetic build approach with cachi2 and add
support for multiple architectures (x64, arm64, s390x, ppc64) in yarn
configuration. This resolves hermetic build failures on non-x86_64
architectures by ensuring all required architecture-specific packages
are included in dependency resolution.

The change simplifies the build process by removing complex corepack
setup and cachito integration in favor of the standard hermetic build
pattern used across OpenShift components.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 8, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: edcf5165-768f-44ba-ad03-fa4c6851bdb4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@logonoff
Copy link
Copy Markdown
Member Author

logonoff commented May 9, 2026

/label backport-risk-assessed
/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 9, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented May 9, 2026

@logonoff: This PR has been marked as verified by CI.

Details

In response to this:

/label backport-risk-assessed
/verified by CI

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 backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label May 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@sanketpathak sanketpathak

Labels

backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@logonoff @openshift-ci-robot @sanketpathak @lgarciaaco