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.

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
4 changes: 4 additions & 0 deletions website/blog/2023-10-31-to-defer-or-to-clone.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,6 +91,10 @@ Using the cheat sheet above, let’s explore a few common scenarios and explore

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

:::tip Use `dbt clone` in CI jobs
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved
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.
:::

In this scenario, we want to:
1. Refer to production models wherever possible to speed up continuous integration (CI) runs
2. Only run and test models in the CI staging environment that have changed from the production environment
Expand Down
Loading