ci: separate out build steps per platform

[de-sh]

Fixes #XXXX.

Description

---

This PR has:

• been tested to ensure log ingestion and log query works.
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added documentation for new or modified features or behaviors.

Summary by CodeRabbit

• New Features
  • Improved our container build process to support dedicated image builds for both x86_64 and aarch64 platforms, offering enhanced caching and clearer deployment management.

[coderabbitai]

Walkthrough

This update modifies two GitHub Actions workflow files by splitting the Docker build-and-push process into two distinct steps. One step builds and pushes the image for the x86_64 architecture, while the other targets aarch64. Both steps now explicitly specify their target platforms and include caching configurations to optimize the builds.

Changes

File(s)	Change Summary
.github/workflows/build-push-edge-debug.yaml, .github/workflows/build-push-edge.yaml	Split the Docker build-and-push process into two steps: one renamed to "Build and push x86_64" (targeting linux/amd64) and a new or updated "Build and push aarch64" step (targeting linux/arm64). Caching settings (cache-from and cache-to) are applied to both steps for improved build efficiency.

Sequence Diagram(s)

sequenceDiagram
    participant Runner as CI Workflow Runner
    participant Step1 as Build and push x86_64
    participant Step2 as Build and push aarch64
    participant DockerAction as docker/build-push-action

    Runner->>Step1: Trigger build for linux/amd64
    Step1->>DockerAction: Execute build & push (linux/amd64)
    DockerAction-->>Step1: Return build status
    Runner->>Step2: Trigger build for linux/arm64
    Step2->>DockerAction: Execute build & push (linux/arm64)
    DockerAction-->>Step2: Return build status

Loading

Poem

I hopped through the code with delight,
Two paths to build by day and night.
x86_64 leads the way so true,
While aarch64 follows, fresh as dew.
A rabbit’s cheer for changes bright! 🐇💻

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3d519d4 and bbdaed6.

📒 Files selected for processing (1)

• .github/workflows/build-push-edge.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (10)

• GitHub Check: Build Default x86_64-pc-windows-msvc
• GitHub Check: Build Default aarch64-apple-darwin
• GitHub Check: Build Default x86_64-apple-darwin
• GitHub Check: Build Default aarch64-unknown-linux-gnu
• GitHub Check: Build Default x86_64-unknown-linux-gnu
• GitHub Check: Build Kafka aarch64-apple-darwin
• GitHub Check: coverage
• GitHub Check: Build Kafka x86_64-unknown-linux-gnu
• GitHub Check: Quest Smoke and Load Tests for Distributed deployments
• GitHub Check: Quest Smoke and Load Tests for Standalone deployments

🔇 Additional comments (2)

.github/workflows/build-push-edge.yaml (2)

40-51: Separation for x86_64 Build Step: Clear Distinction Established
The new "Build and push x86_64" step is well-configured to build for the x86_64 architecture:

• It correctly uses ./Dockerfile and the image tag parseable/parseable:edge, which aligns with prior review suggestions.
• The platforms field is explicitly set to linux/amd64, ensuring the build is tailored for x86_64 systems.
• Caching options (cache-from and cache-to) are set to optimize build performance.

This change clearly meets the PR objective of separating the build steps per platform.

---

52-61: Tailored aarch64 Build Step: Platform Specificity Updated
The updated "Build and push aarch64" step now targets only the linux/arm64 platform:

• The configuration uses ./Dockerfile properly and tags the image as parseable/parseable, which seems intentional for the aarch64 build.
• The explicit platform setting ensures that the build is isolated from the x86_64 process, aligning with the separation goal.
• Caching is consistently configured as with the other step.

Please verify that using the tag parseable/parseable (without an architecture suffix) meets your versioning and deployment expectations for aarch64 images.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.