Temporary QEMU fix for CI beskar-ostree image build

[cclerget]

Summary by CodeRabbit

• New Features
  • Integrated QEMU setup in CI/CD workflows for improved cross-platform testing.
• Refactor
  • Enhanced build process to support QEMU for non-native platform builds.

[coderabbitai]

Walkthrough

The project has embraced improvements for cross-platform builds by incorporating QEMU, an open-source machine emulator and virtualizer. This enhancement allows for seamless creation of container images for multiple CPU architectures directly within the CI/CD pipeline, ensuring broader compatibility and streamlined development workflows.

Changes

File	Summary
.github/workflows/release.yml	Added "Set up QEMU" step using docker/setup-qemu-action@v3
build/mage/build.go	Added useQEMUForCIImage in binaryConfig and logic in build function for container options on non-native platforms

🐇✨
In the realm of code, a leap was made,
Across platforms, our builds now parade.
With QEMU's embrace, and Docker's grace,
Our binaries dance in a seamless space.
🚀🌌

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 286779e and a48ca6e.

Files selected for processing (2)

• .github/workflows/release.yml (1 hunks)
• build/mage/build.go (3 hunks)

Additional comments: 3

.github/workflows/release.yml (1)

• 82-83: The addition of the "Set up QEMU" step using docker/setup-qemu-action@v3 is correctly implemented and follows best practices for GitHub Actions workflows. This step is essential for ensuring compatibility and reliability across various computing architectures during the CI process.

build/mage/build.go (2)

• 52-52: The addition of the useQEMUForCIImage field to the binaryConfig struct is correctly implemented. This field is crucial for enabling conditional logic that leverages QEMU for image builds on non-native platforms, aligning with the PR objectives to enhance cross-platform compatibility.
• 306-310: The logic introduced to utilize the useQEMUForCIImage field when setting container options for non-native platforms is correctly implemented. This conditional logic ensures that QEMU is leveraged for image builds on non-native platforms, enhancing the build process's compatibility and reliability across various computing architectures.