ci: re-enabled intel build pipeline

[Thammachart]

Intel build pipeline has been unclogged, container images now published without out of space error

ref:

• ci: free_disk_space flag enabled for intel variant ggml-org/llama.cpp#13426
• llama.cpp github actions
• latest intel container image

Summary by CodeRabbit

• Chores
  • Updated CI workflow to include the "intel" platform in build and push processes.

[coderabbitai]

Walkthrough

The GitHub Actions workflow configuration was updated to add the "intel" platform to the build matrix for the "build-and-push" job. This change ensures that the continuous integration process now includes building and pushing images for the "intel" platform alongside the existing platforms.

Changes

File(s)	Change Summary
.github/workflows/containers.yml	Added "intel" to the build matrix in the "build-and-push" job, enabling CI builds for this platform.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub Actions
    participant Build System

    Developer->>GitHub Actions: Push code / open PR
    GitHub Actions->>Build System: Trigger build-and-push for each platform (cuda, vulkan, cpu, musa, intel)
    Build System-->>GitHub Actions: Build and push images for all platforms including intel
    GitHub Actions-->>Developer: Report build status for all platforms

Loading

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

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

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/containers.yml (1)

18-18: Consider switching to a block-style YAML list for matrix platforms.

Using a block-style list can improve readability and make diffs cleaner when adding or removing entries:

strategy:
  matrix:
    platform:
      - intel
      - cuda
      - vulkan
      - cpu
      - musa

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5c5a5da and 1d6d96d.

📒 Files selected for processing (1)

• .github/workflows/containers.yml (1 hunks)

🔇 Additional comments (1)

.github/workflows/containers.yml (1)

18-18: Verify build script compatibility with the new intel target.

You’ve added intel back into the build matrix, but please confirm that ./docker/build-container.sh (and any underlying Docker Buildx/platform mappings) correctly recognize and handle "intel" as a platform key. Run a CI trial or smoke test to ensure image builds and pushes for the intel target succeed without errors.