From ecf738db887c811cdc5b063e79cec35b313741b3 Mon Sep 17 00:00:00 2001 From: Jeremy Yeo Date: Fri, 20 Dec 2024 09:48:03 +1300 Subject: [PATCH 1/3] Update ci-jobs.md --- website/docs/docs/deploy/ci-jobs.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/website/docs/docs/deploy/ci-jobs.md b/website/docs/docs/deploy/ci-jobs.md index 38bfb56a72..57cb406b4f 100644 --- a/website/docs/docs/deploy/ci-jobs.md +++ b/website/docs/docs/deploy/ci-jobs.md @@ -190,6 +190,15 @@ To validate _all_ semantic nodes in your project, add the following command to d + + +Scenarios where dbt Cloud will not run a CI job using the ADO native integration: + +- If you have abandoned a previous PR (e.g. PR 1) that had triggered a CI job (e.g. merging `feature-123` into `main`) and then opened up a new PR (PR 2) that also merges `feature-123` into `main` - PR 2 will not trigger a new CI job. +- A previous PR (e.g. PR 1) that was on commit `#4818ceb` triggered a CI job. You now create a new PR (e.g. PR 2) that is also on the same commit `#4818ceb` - PR 2 will not trigger a new CI job. + + + If your temporary schemas aren't dropping after a PR merges or closes, this typically indicates one of these issues: - You have overridden the generate_schema_name macro and it isn't using dbt_cloud_pr_ as the prefix. From 2dcacb852dfc2cd83037bd540cd7e62090930d22 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 20 Dec 2024 09:47:32 +0000 Subject: [PATCH 2/3] Update ci-jobs.md --- website/docs/docs/deploy/ci-jobs.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/website/docs/docs/deploy/ci-jobs.md b/website/docs/docs/deploy/ci-jobs.md index 57cb406b4f..0d8840e881 100644 --- a/website/docs/docs/deploy/ci-jobs.md +++ b/website/docs/docs/deploy/ci-jobs.md @@ -190,12 +190,17 @@ To validate _all_ semantic nodes in your project, add the following command to d - + -Scenarios where dbt Cloud will not run a CI job using the ADO native integration: +dbt Cloud won't trigger a CI job run if the latest commit in a pull or merge request has already triggered a run for that job. However, some providers (like GitHub) will enforce the result of the existing run on multiple pull/merge requests. -- If you have abandoned a previous PR (e.g. PR 1) that had triggered a CI job (e.g. merging `feature-123` into `main`) and then opened up a new PR (PR 2) that also merges `feature-123` into `main` - PR 2 will not trigger a new CI job. -- A previous PR (e.g. PR 1) that was on commit `#4818ceb` triggered a CI job. You now create a new PR (e.g. PR 2) that is also on the same commit `#4818ceb` - PR 2 will not trigger a new CI job. +Scenarios where dbt Cloud does not trigger a CI job with Azure DevOps: + +1. Reusing a branch in a new PR + - If you abandon a previous PR (PR 1) that triggered a CI job for the same branch (`feature-123`) merging into `main`, and then open a new PR (PR 2) with the same branch merging into main — dbt Cloud won't trigger a new CI job for PR 2. + +2. Reusing the same commit + - If you create a new PR (PR 2) on the same commit (`#4818ceb`) as a previous PR (PR 1) that triggered a CI job — dbt Cloud won't trigger a new CI job for PR 2. From 696494bc7c45fc6a12d04851fa9ef4c34fd7f774 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 20 Dec 2024 09:48:15 +0000 Subject: [PATCH 3/3] Update website/docs/docs/deploy/ci-jobs.md --- website/docs/docs/deploy/ci-jobs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/deploy/ci-jobs.md b/website/docs/docs/deploy/ci-jobs.md index 0d8840e881..08c7813bfd 100644 --- a/website/docs/docs/deploy/ci-jobs.md +++ b/website/docs/docs/deploy/ci-jobs.md @@ -197,7 +197,7 @@ dbt Cloud won't trigger a CI job run if the latest commit in a pull or merge req Scenarios where dbt Cloud does not trigger a CI job with Azure DevOps: 1. Reusing a branch in a new PR - - If you abandon a previous PR (PR 1) that triggered a CI job for the same branch (`feature-123`) merging into `main`, and then open a new PR (PR 2) with the same branch merging into main — dbt Cloud won't trigger a new CI job for PR 2. + - If you abandon a previous PR (PR 1) that triggered a CI job for the same branch (`feature-123`) merging into `main`, and then open a new PR (PR 2) with the same branch merging into`main` — dbt Cloud won't trigger a new CI job for PR 2. 2. Reusing the same commit - If you create a new PR (PR 2) on the same commit (`#4818ceb`) as a previous PR (PR 1) that triggered a CI job — dbt Cloud won't trigger a new CI job for PR 2.