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

Update ci-jobs.md #6696

Merged
merged 3 commits into from
Dec 20, 2024
Merged

Update ci-jobs.md #6696

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ecf738d
Update ci-jobs.md
jeremyyeo Dec 19, 2024
2dcacb8
Update ci-jobs.md
mirnawong1 Dec 20, 2024
696494b
Update website/docs/docs/deploy/ci-jobs.md
mirnawong1 Dec 20, 2024
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
14 changes: 14 additions & 0 deletions website/docs/docs/deploy/ci-jobs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -190,6 +190,20 @@ To validate _all_ semantic nodes in your project, add the following command to d

<FAQ path="Troubleshooting/gitlab-webhook"/>

<DetailsToggle alt_header="CI jobs aren't triggering occasionally when opening a PR using the Azure DevOps (ADO) 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.

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` &mdash; 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 &mdash; dbt Cloud won't trigger a new CI job for PR 2.

</DetailsToggle>

<DetailsToggle alt_header="Temporary schemas aren't dropping">
If your temporary schemas aren't dropping after a PR merges or closes, this typically indicates one of these issues:
- You have overridden the <code>generate_schema_name</code> macro and it isn't using <code>dbt_cloud_pr_</code> as the prefix.
Expand Down
Loading