apps/docs/content/docs/guides/ci-vendors/index.mdx
Turborepo not only speeds up builds, but also the rest of your Continuous Integration pipeline by using Remote Caching. Below are a few platform recipes to use Turborepo with your CI providers.
<Cards><Card title="Vercel (Zero configuration)" href="/docs/guides/ci-vendors/vercel" />
<Card title="GitHub Actions" href="/docs/guides/ci-vendors/github-actions" /> <Card title="CircleCI" href="/docs/guides/ci-vendors/circleci" /> <Card title="GitLab CI" href="/docs/guides/ci-vendors/gitlab-ci" /> <Card title="Travis CI" href="/docs/guides/ci-vendors/travis-ci" /> <Card title="Buildkite" href="/docs/guides/ci-vendors/buildkite" /> </Cards>To enable Remote Caching for your CI:
| Variable | Description |
|---|---|
TURBO_TOKEN | The Bearer token to access the Remote Cache |
TURBO_TEAM | The account name associated with your repository. When using <a href="https://vercel.com/docs/monorepos/remote-caching#vercel-remote-cache" rel="noreferrer noopener" target="_blank">Vercel Remote Cache</a>, this is your team's slug. |
turbo.