Fast-follows for merge jobs #5308
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
github-actions
bot
added
size: small
nghi-ly
commented
Apr 18, 2024
nghi-ly
commented
Apr 18, 2024
| @@ -509,7 +515,7 @@ Additionally, you’ll see the job in the run history of dbt Cloud. It should be | |||
|
|
|||
| If your git provider is not one with a native integration with dbt Cloud, but you still want to take advantage of CI builds, you've come to the right spot! With just a bit of work it's possible to setup a job that will run a dbt Cloud job when a pull request (PR) is created. | |||
|
|
|||
| :::info Run on PR | |||
| :::tip Run on PR | |||
|
|
|||
| If your git provider has a native integration with dbt Cloud, you can take advantage of the setup instructions [here](/docs/deploy/ci-jobs). | |||
There was a problem hiding this comment.
for consistency and parallel construction, new callout on line 61 follows this ^ format
nghi-ly
commented
Apr 18, 2024
joellabes
approved these changes
Apr 18, 2024
mirnawong1
reviewed
Apr 22, 2024
|
|
||
| You can set up a merge job to implement a continuous development (CD) workflow in dbt Cloud. The merge job triggers a dbt job to run when someone merges Git pull requests into production. This creates a seamless development experience where changes made in code will automatically update production data. | ||
|
|
||
| By using CD in dbt Cloud, you can take advantage of deferral to build only the edited model and any downstream changes. With merge jobs, state will be updated almost instantly, always giving the most up-to-date state information in [dbt Explorer](/docs/collaborate/explore-projects). | ||
|
|
||
| ## Prerequisites | ||
| - You have a dbt Cloud account. | ||
| - You have access to the beta release for this functionality. | ||
| - You have set up a [connection with your Git provider](/docs/cloud/git/git-configuration-in-dbt-cloud). This integration lets dbt Cloud run jobs on your behalf for job triggering. | ||
| - If you're using a native [GitLab](/docs/cloud/git/connect-gitlab) integration, you need a paid or self-hosted account that includes support for GitLab webhooks and [project access tokens](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html). If you're using GitLab Free, merge requests will trigger CI jobs but CI job status updates (success or failure of the job) will not be reported back to GitLab. |
There was a problem hiding this comment.
active voice sugg
Suggested change
| - If you're using a native [GitLab](/docs/cloud/git/connect-gitlab) integration, you need a paid or self-hosted account that includes support for GitLab webhooks and [project access tokens](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html). If you're using GitLab Free, merge requests will trigger CI jobs but CI job status updates (success or failure of the job) will not be reported back to GitLab. | |
| - If you're using a native [GitLab](/docs/cloud/git/connect-gitlab) integration, you need a paid or self-hosted account that includes support for GitLab webhooks and [project access tokens](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html). If you're using GitLab Free, merge requests will trigger CI jobs but GitLab won't report back the CI job status updates (success or failure of the job). |
There was a problem hiding this comment.
like your sugg but it changes the meaning of the sentence (updates not reported to GitLab vs GitLab not reporting updates)
mirnawong1
reviewed
Apr 22, 2024
| @@ -58,6 +58,12 @@ Here’s a quick look at what this pipeline will accomplish: | |||
|
|
|||
| This job will take a bit more to setup, but is a good example of how to call the dbt Cloud API from a CI/CD pipeline. The concepts presented here can be generalized and used in whatever way best suits your use case. | |||
|
|
|||
| :::tip Run on merge | |||
|
|
|||
| If your Git provider has a native integration with dbt Cloud, you can take advantage of setting up [Merge jobs](/docs/deploy/merge-jobs) in the UI. | |||
mirnawong1
approved these changes
Apr 22, 2024
There was a problem hiding this comment.
looks awesome, thanks @nghi-ly and small non blocker from me!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you changing in this pull request and why?
Checklist