Skip to content

Use WarpBuild runners for CI workflows#661

Open
tillrohrmann wants to merge 1 commit intorestatedev:mainfrom
tillrohrmann:warpbuild-runners
Open

Use WarpBuild runners for CI workflows#661
tillrohrmann wants to merge 1 commit intorestatedev:mainfrom
tillrohrmann:warpbuild-runners

Conversation

@tillrohrmann
Copy link
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, release-docs, template tests, and compatibility 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, release-docs, template tests, and compatibility
workflows are left on GitHub-hosted runners.
tags: restatedev/typescript-test-services
cache-from: type=gha,scope=${{ github.workflow }}
cache-to: type=gha,mode=max,scope=${{ github.workflow }}
cache-from: type=gha,url=http://127.0.0.1:49160/,version=1,scope=${{ github.workflow }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know what this thing is? but I trust you've checked this, and that make sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants