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

Jump to bottom

Update ci-jobs.md #5899

Merged
merged 2 commits into from
Aug 7, 2024
Merged

Update ci-jobs.md #5899

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
58d56b2
Update ci-jobs.md
Tonayya Aug 7, 2024
a740ca1
Update website/docs/docs/deploy/ci-jobs.md
mirnawong1 Aug 7, 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
4 changes: 3 additions & 1 deletion website/docs/docs/deploy/ci-jobs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -216,7 +216,9 @@ If you're on a Virtual Private dbt Enterprise plan using security features like

When you start a CI job, the pull request status should show as `pending` while it waits for an update from dbt. Once the CI job finishes, dbt sends the status to Azure DevOps (ADO), and the status will change to either `succeeded` or `failed`.

If the status doesn't get updated after the job runs, check if there are any git branch policies in place that's blocking ADO from receiving these updates. You can find relevant information here:
If the status doesn't get updated after the job runs, check if there are any git branch policies in place that's blocking ADO from receiving these updates. An example of a branch policy that would result in this issue is enabling "Reset conditions" under "Status checks". If you toggle on "Reset status whenever there are new changes", this will impact dbt's ability to update ADO about the status of your CI job run.
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved
You can find relevant information here:
- [Azure DevOps Services Status checks](https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies?view=azure-devops&tabs=browser#status-checks)
- [Azure DevOps Services Pull Request Stuck Waiting on Status Update](https://support.hashicorp.com/hc/en-us/articles/18670331556627-Azure-DevOps-Services-Pull-Request-Stuck-Waiting-on-Status-Update-from-Terraform-Cloud-Enterprise-Run)
- [Pull request status](https://learn.microsoft.com/en-us/azure/devops/repos/git/pull-request-status?view=azure-devops#pull-request-status)

Expand Down
Loading