-
Notifications
You must be signed in to change notification settings - Fork 977
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 repo caching #4684
Update repo caching #4684
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -42,6 +42,13 @@ For improved reliability and performance on your job runs, you can enable dbt Cl | |||
|
|||
dbt Cloud caches your project's Git repo after each successful run and retains it for 8 days if there are no repo updates. It caches all packages regardless of installation method and does not fetch code outside of the job runs. | |||
|
|||
Below lists the situations when dbt Cloud uses the cached copy: | |||
|
|||
- Outages from third-party services (for example, your Git provider). |
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.
adding a non git related service to be extra explicit
- Outages from third-party services (for example, your Git provider). | |
- Outages from third-party services (for example, the [dbt package hub](https://hub.getdbt.com/)). |
Co-authored-by: mirnawong1 <[email protected]>
Co-authored-by: mirnawong1 <[email protected]>
Co-authored-by: mirnawong1 <[email protected]>
Co-authored-by: mirnawong1 <[email protected]>
@@ -42,6 +42,13 @@ For improved reliability and performance on your job runs, you can enable dbt Cl | |||
|
|||
dbt Cloud caches your project's Git repo after each successful run and retains it for 8 days if there are no repo updates. It caches all packages regardless of installation method and does not fetch code outside of the job runs. | |||
|
|||
dbt Cloud will use the cached copy of your project's Git repo under these circumstances: | |||
|
|||
- Outages from third-party services (for example, the [dbt package hub](https://hub.getdbt.com/)). |
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.
i think it is helpful to have another example, on top of your git one. so adding the git bc that's def a big example that would be helpful for users to know
- Outages from third-party services (for example, the [dbt package hub](https://hub.getdbt.com/)). | |
- Outages from third-party services (for example, your Git provider or the [dbt package hub](https://hub.getdbt.com/)). |
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.
the Git example is actually mentioned in the screenshot so we're good there
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.
non blocker suggestion and am approving to not block you. lgtm and repo caching is so cool!
What are you changing in this pull request and why?
Update repo caching section below so it includes info about the situations when dbt Cloud uses the cached copy instead
https://docs.getdbt.com/docs/deploy/deploy-environments#git-repository-caching
Checklist