Skip to content

Use WarpBuild runners for CI workflows#105

Merged
slinkydeveloper merged 1 commit into
restatedev:mainfrom
tillrohrmann:warpbuild-runners
Mar 27, 2026
Merged

Use WarpBuild runners for CI workflows#105
slinkydeveloper merged 1 commit into
restatedev:mainfrom
tillrohrmann:warpbuild-runners

Conversation

@tillrohrmann

Copy link
Copy Markdown
Contributor

Summary

  • Migrate CI and integration workflows to warp-ubuntu-latest-x64-4x
  • In ci.yml, disable the built-in Swatinem/rust-cache from actions-rust-lang/setup-rust-toolchain and add explicit WarpBuilds/rust-cache@v2 for WarpBuild-optimized caching
  • Update Docker Buildx setup with network=host driver-opts for WarpBuild compatibility
  • Point Docker layer cache (cache-from/cache-to) at WarpBuild's cache proxy (http://127.0.0.1:49160/)
  • CLA workflow is left on GitHub-hosted runners

Migrate CI and integration workflows to warp-ubuntu-latest-x64-4x.
In ci.yml, disable the built-in Swatinem/rust-cache from
setup-rust-toolchain and add explicit WarpBuilds/rust-cache for
WarpBuild-optimized caching. Update Docker Buildx setup with
network=host driver-opts and point Docker layer cache at WarpBuild's
cache proxy. CLA workflow is left on GitHub-hosted runners.
@slinkydeveloper slinkydeveloper merged commit e049ec9 into restatedev:main Mar 27, 2026
3 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Mar 27, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants