Skip to content

ci : split build.yml + server.yml#20546

Merged
ggerganov merged 7 commits intomasterfrom
gg/ci-build-split
Mar 15, 2026
Merged

ci : split build.yml + server.yml#20546
ggerganov merged 7 commits intomasterfrom
gg/ci-build-split

Conversation

@ggerganov
Copy link
Copy Markdown
Member

@ggerganov ggerganov commented Mar 14, 2026

cont #20540

  • Split build.yml + server.yml into parts and move some of the workflows in the new parts
  • Continue to run build.yml + server.yml on all PRs and master branch
  • The new build parts run only on master branch
  • The new build parts can be manually triggered on PRs
  • Fork and use setup-xcode action
  • Rename workflow: drop -cmake, improve consistency
  • Rename ggml-ci-arm64-graviton4-kleidiai -> ggml-ci-arm64-cpu-kleidiai-graviton4
  • Remove ubuntu-llguidance-riscv64-native
  • Remove ubuntu-cmake-rpc-riscv64-native

Note: not sure how the GA cache works, but I suspect that when we run this new CI it will trash the caches because of the new workflow names

Next PRs

@github-actions github-actions Bot added the devops improvements to build systems and github actions label Mar 14, 2026
@CISC
Copy link
Copy Markdown
Member

CISC commented Mar 14, 2026

Note: not sure how the GA cache works, but I suspect that when we run this new CI it will trash the caches because of the new workflow names

Since you also renamed the keys, yes, but since we just about can't fit a whole run in the 10GB we have available we are partially thrashing the cache already. This will just leave older PRs in the dark until they catch up, not a major issue I think.

Base automatically changed from gg/ci-build-self-hosted to master March 14, 2026 21:15
@ggerganov ggerganov changed the title ci : split build.yml ci : split build.yml + server.yml Mar 15, 2026
@ggerganov
Copy link
Copy Markdown
Member Author

I moved the sanitizer workflows in separate *-sanitize.yml files to be executed manually on PRs.

In the next PR, I think we can move some of the ggml-ci CPU workflows to self-hosted runners since we have both x86 and arm64 machines enrolled now. This will probably free up some GH cache.

@ggerganov ggerganov marked this pull request as ready for review March 15, 2026 10:20
@ggerganov ggerganov requested a review from CISC as a code owner March 15, 2026 10:20
Comment thread .github/workflows/build-3rd-party.yml Outdated
Comment thread .github/workflows/build-apple.yml Outdated
Comment thread .github/workflows/build-cann.yml Outdated
Comment thread .github/workflows/build-riscv.yml Outdated
Comment thread .github/workflows/build-sanitize.yml Outdated
Comment thread .github/workflows/build-vulkan.yml Outdated
Comment thread .github/workflows/server-sanitize.yml Outdated
@ggerganov
Copy link
Copy Markdown
Member Author

I think we should drop the spacemit cache:

image

The build-riscv.yml should run only on changes to ggml/src/ggml-cpu/spacemit/* and should not use the GH cache.

@CISC
Copy link
Copy Markdown
Member

CISC commented Mar 15, 2026

I think we should drop the spacemit cache:
image

The build-riscv.yml should run only on changes to ggml/src/ggml-cpu/spacemit/* and should not use the GH cache.

It's not running on riscv, it's a crossbuild, IIRC it's a special arch.

@ggerganov
Copy link
Copy Markdown
Member Author

The #20585 and #20588 should free quite some GH cache too.

@ggerganov
Copy link
Copy Markdown
Member Author

  • Extracted the android builds to run only on master
  • For the split workflows, they now also run in the PRs if files are touched directly. For example, modifying ggml-metal sources will trigger the build-apple.yml workflow even in the PRs

Comment thread .github/workflows/release.yml Outdated
[no ci]

Co-authored-by: Sigbjørn Skjæret <sigbjorn.skjaeret@scala.com>
@ggerganov
Copy link
Copy Markdown
Member Author

I think I'll yolo this into master and see what happens.

@ggerganov ggerganov merged commit 9cd4ebc into master Mar 15, 2026
1 check passed
@ggerganov ggerganov deleted the gg/ci-build-split branch March 15, 2026 13:11
@CISC
Copy link
Copy Markdown
Member

CISC commented Mar 15, 2026

I think I'll yolo this into master and see what happens.

https://github.com/ggml-org/llama.cpp/actions/runs/23111057141/job/67128454775

@ggerganov
Copy link
Copy Markdown
Member Author

Should be fixed now - I incorrectly forked only the master branch earlier.

Ethan-a2 pushed a commit to Ethan-a2/llama.cpp that referenced this pull request Mar 20, 2026
* ci : split build.yml

* cont : split server.yml

* cont : reduce paths

* cont : split build-android.yml + update paths

* ci : make msys workflows manual (ggml-org#20588)

* ci : make cross-build workflows manual (ggml-org#20585)

* cont : fix release paths

Co-authored-by: Sigbjørn Skjæret <sigbjorn.skjaeret@scala.com>

---------

Co-authored-by: Sigbjørn Skjæret <sigbjorn.skjaeret@scala.com>
Seunghhon pushed a commit to Seunghhon/llama.cpp that referenced this pull request Apr 26, 2026
* ci : split build.yml

* cont : split server.yml

* cont : reduce paths

* cont : split build-android.yml + update paths

* ci : make msys workflows manual (ggml-org#20588)

* ci : make cross-build workflows manual (ggml-org#20585)

* cont : fix release paths

Co-authored-by: Sigbjørn Skjæret <sigbjorn.skjaeret@scala.com>

---------

Co-authored-by: Sigbjørn Skjæret <sigbjorn.skjaeret@scala.com>
rsenthilkumar6 pushed a commit to rsenthilkumar6/llama.cpp that referenced this pull request May 1, 2026
* ci : split build.yml

* cont : split server.yml

* cont : reduce paths

* cont : split build-android.yml + update paths

* ci : make msys workflows manual (ggml-org#20588)

* ci : make cross-build workflows manual (ggml-org#20585)

* cont : fix release paths

Co-authored-by: Sigbjørn Skjæret <sigbjorn.skjaeret@scala.com>

---------

Co-authored-by: Sigbjørn Skjæret <sigbjorn.skjaeret@scala.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

devops improvements to build systems and github actions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants