Skip to content

Commit

Permalink
Update website/docs/guides/set-up-ci.md
Browse files Browse the repository at this point in the history
  • Loading branch information
mirnawong1 authored Jul 16, 2024
1 parent b54ae38 commit f31b3a3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion website/docs/guides/set-up-ci.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ In the Execution Settings, your command will be preset to `dbt build --select st
To be able to find modified nodes, dbt needs to have something to compare against. dbt Cloud uses the last successful run of any job in your Production environment as its [comparison state](/reference/node-selection/syntax#about-node-selection). As long as you identified your Production environment in Step 2, you won't need to touch this. If you didn't, pick the right environment from the dropdown.

:::info Use CI to test your metrics
If you've [built metric definition models](/docs/build/build-metrics-intro) in your dbt project, you can [test and validate them in CI](/docs/deploy/ci-jobs#test-metrics-in-ci) to ensure code changes made to dbt models don't break these metrics.
If you've [built semantic nodes](/docs/build/build-metrics-intro) in your dbt project, you can [validate them in a CI job](/docs/deploy/ci-jobs#semantic-validations-in-ci) to ensure code changes made to dbt models don't break these metrics.
:::

### 3. Test your process
Expand Down

0 comments on commit f31b3a3

Please sign in to comment.