Skip to content
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

link to clone in ci job best practices #4665

Merged
merged 7 commits into from
Dec 18, 2023
Merged

link to clone in ci job best practices #4665

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
eca769c
link to clone in ci job best practices
mirnawong1 Dec 18, 2023
c1a6d9c
Update website/blog/2023-10-31-to-defer-or-to-clone.md
mirnawong1 Dec 18, 2023
301c8a9
Update website/blog/2023-10-31-to-defer-or-to-clone.md
mirnawong1 Dec 18, 2023
7d81a53
Update 2023-10-31-to-defer-or-to-clone.md
mirnawong1 Dec 18, 2023
25c2af9
Update 2023-10-31-to-defer-or-to-clone.md
mirnawong1 Dec 18, 2023
a18c76e
Merge branch 'current' into mwong-add-clone-guide
mirnawong1 Dec 18, 2023
5996a31
Merge branch 'current' into mwong-add-clone-guide
matthewshaver Dec 18, 2023
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
8 changes: 6 additions & 2 deletions website/blog/2023-10-31-to-defer-or-to-clone.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ Using the cheat sheet above, let’s explore a few common scenarios and explore
1. Make a copy of our production dataset available in our downstream BI tool
2. To safely iterate on this copy without breaking production datasets

Therefore, we should use **clone** in this scenario
Therefore, we should use **clone** in this scenario.

2. **[Slim CI](https://discourse.getdbt.com/t/how-we-sped-up-our-ci-runs-by-10x-using-slim-ci/2603)**

Expand All @@ -96,7 +96,11 @@ Using the cheat sheet above, let’s explore a few common scenarios and explore
2. Only run and test models in the CI staging environment that have changed from the production environment
3. Reference models from different environments – prod for unchanged models, and staging for modified models

Therefore, we should use **defer** in this scenario
Therefore, we should use **defer** in this scenario.

:::tip Use `dbt clone` in CI jobs to test incremental models
Learn how to [use `dbt clone` in CI jobs](/best-practices/clone-incremental-models) to efficiently test modified incremental models, simulating post-merge behavior while avoiding full-refresh costs.
:::

3. **[Blue/Green Deployments](https://discourse.getdbt.com/t/performing-a-blue-green-deploy-of-your-dbt-project-on-snowflake/1349)**

Expand Down
Loading