Skip to content

Use WarpBuild runners for CI workflows#185

Merged
slinkydeveloper merged 1 commit intorestatedev:mainfrom
tillrohrmann:warpbuild-runners
Mar 23, 2026
Merged

Use WarpBuild runners for CI workflows#185
slinkydeveloper merged 1 commit intorestatedev:mainfrom
tillrohrmann:warpbuild-runners

Conversation

@tillrohrmann
Copy link
Copy Markdown
Contributor

Summary

  • Migrate test, integration, and docker workflows from ubuntu-latest to warp-ubuntu-latest-x64-4x
  • 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/)
  • Upgrade docker/setup-buildx-action from v2 to v3 in docker.yml
  • Release and CLA workflows are left on GitHub-hosted runners

Migrate test, integration, and docker workflows from ubuntu-latest to
warp-ubuntu-latest-x64-4x. Update Docker Buildx setup with
network=host driver-opts and point Docker layer cache at WarpBuild's
cache proxy. Release and CLA workflows are left on GitHub-hosted
runners.
@slinkydeveloper slinkydeveloper merged commit 538d03c into restatedev:main Mar 23, 2026
7 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Mar 23, 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