Git providers supporting CI #6692
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
Co-authored-by: Mirna Wong <[email protected]>
Co-authored-by: Mirna Wong <[email protected]>
Co-authored-by: Mirna Wong <[email protected]>
Co-authored-by: Mirna Wong <[email protected]>
| @@ -0,0 +1,2 @@ | |||
| If you're not using dbt Cloud’s native Git integration with [GitHub](/docs/cloud/git/connect-github), [GitLab](/docs/cloud/git/connect-gitlab), or [Azure DevOps](/docs/cloud/git/connect-azure-devops), you can use the [Administrative API](/docs/dbt-cloud-apis/admin-cloud-api) to trigger a CI job to run. However, dbt Cloud will not automatically delete the temporary schema for you. This is because automatic deletion relies on incoming webhooks from Git providers, which is only available through the native integrations. | |||
There was a problem hiding this comment.
this is a silly question but why are you turning this into a snippet? and why isn't it be used if turning into a snippet?
There was a problem hiding this comment.
it seems that that content is part of this section: https://docs.getdbt.com/docs/deploy/ci-jobs#trigger-a-ci-job-with-the-api
| @@ -0,0 +1,8 @@ | |||
| If your git provider has a native dbt Cloud integration, you can set up [continuous integration (CI) job](/docs/deploy/ci-jobs) within dbt Cloud. For providers without native integration, you can still use a Git URL. The following table explains the available integration options and their capabilities. | |||
There was a problem hiding this comment.
also for this snippet, to address Joel's issue and my suggestion -- should this snippet table also be used in the git configuration page (e.g. maybe the landing page or git url page)?
t'd be useful to just have that listed in the CI docs as well as the configure git docs
There was a problem hiding this comment.
looks much better, thanks for linking the snippet in other pages @nataliefiann ! approved and one question that can be followed up with another pr - should the table include api functionality? eg how you can trigger a job via the cloud api: https://docs.getdbt.com/docs/deploy/ci-jobs#trigger-a-ci-job-with-the-api?
What are you changing in this pull request and why?
I've created this PR with reference to this git issue: #3704 to help users clarify which Git providers support CI.
In the PR, I have updated the Continuous integration page, created a card on the Git configuaration page and linked the table I created in the CI doc to it. I also created and used a snippet from https://docs.getdbt.com/docs/deploy/ci-jobs#trigger-a-ci-job-with-the-api
Update - I've also added the snippet to the Import a project by git URL and Continuous integration jobs in dbt Cloud pages.
Closes: #3704
Checklist
🚀 Deployment available! Here are the direct links to the updated files: