这是indexloc提供的服务，不要输入任何密码
Skip to content

Add a codeblock showing how to run a pipeline #140

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 9, 2021
Merged

Add a codeblock showing how to run a pipeline #140

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
163244b
Add a codeblock explaining how to run a pipeline
dglsparsons Dec 9, 2021
0933bee
Update pipelines.mdx
jaredpalmer Dec 9, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 13 additions & 5 deletions docs/pages/docs/features/pipelines.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,12 +46,20 @@ An example Pipeline configuration:
}
```

The running order based on the `dependsOn` key above is:
The rough execution order for a given package based on the `dependsOn` keys above will be:

1. `build`
2. `test`
3. `lint`
4. `deploy`
1. `build` once its depdendencies have run their `build` commands
2. `test` once its _own_ `build` command is finished
3. `lint` whenever
4. `deploy` once its _own_ `build`, `test`, and `lint` commands have finished

The full pipeline can then be run:

```bash
npx turbo run build test lint deploy
```

Turborepo will then efficiently schedule exection minimizing idle CPUs.

## Task Dependency Format

Expand Down
2 changes: 1 addition & 1 deletion docs/pages/docs/upgrading-to-v1.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ yarn add turbo -W --dev

As mentioned, Turborepo now provides zero-config Remote Caching through [Vercel](https://vercel.com?utm_source=turborepo.org&utm_medium=referral&utm_campaign=docs-link). Remote Caching is free for all Vercel plans during this transition period. Each Vercel account has a shared Remote Cache. This cache is shared across all enviroments (Development, Preview, and Production).

**Important**: turborepo.com allowed multiple caches (i.e. projects) per team (denoted through `--project` flag). With v1.x caching on Vercel, each Vercel account (user or team) has a single shared Remote Cache. If you were actively using multiple turbprepo.com projects for your team, please let us know in [Discord](https://turborepo.org/discord).
**Important**: turborepo.com allowed multiple caches (i.e. projects) per team (denoted through `--project` flag). With v1.x caching on Vercel, each Vercel account (user or team) has a single shared Remote Cache. If you were actively using multiple turborepo.com projects for your team, please let us know in [Discord](https://turborepo.org/discord).

Please note that we are not migrating cache artifacts to Vercel. We apologize for the slower builds during your migration as you rehydrate your remote cache on Vercel or custom cache infra.

Expand Down