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 1 commit
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
9 changes: 9 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,15 @@ 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 integration">

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.
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved
- 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.
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved

</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