-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Update docs on default outputs #2713
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.
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
Update docs on default outputs #2713
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
a9ea366
to
6ea1478
Compare
d3da1bd
to
8122a0f
Compare
c203db6
to
b41851d
Compare
1ff7964
to
b5b5110
Compare
b41851d
to
71fff2e
Compare
@@ -80,11 +80,11 @@ export interface Pipeline { | |||
* Note: turbo automatically logs stderr/stdout to .turbo/run-<task>.log. This file is | |||
* always treated as a cacheable artifact and never needs to be specified. | |||
* | |||
* Passing an empty array can be used to tell turbo that a task is a side-effect and | |||
* Omitting this key or passing an empty array can be used to tell turbo that a task is a side-effect and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We provide no control over caching of logs. If you cache the task, we cache the logs. We cache by default. Therefore after this change, unless you specify cache: false
in turbo.json
or --no-cache
at runtime this whole discussion is now weird. Given that there is no longer any reason to pass []
here (previously: prevent capturing the things in the default) we should probably reduce this explanation.
The set of glob patterns of a task's cacheable filesystem outputs.
Turborepo captures task logs for all tasks. This enables us to cache tasks whose runs produce no artifacts other than logs, such as linters. These logs are always treated as a cacheable artifact and never need to be specified.
/cc @mattpocock for wordsmith help?
71fff2e
to
4087aa2
Compare
🟢 CI successful 🟢Thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is such a fantastic ergonomics win. 😅
80ef364
to
f2904e6
Compare
Stacked PRs:
turbo@1.7