Update job-scheduler.md #6676
Merged
Update job-scheduler.md #6676
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
Coming newly into the orchestration team, I am updating the initial description of the scheduler types to better align with how users may view the product today: 1. we refer to merge jobs as merge jobs (and it is an explicit category in the UI) so I think it would be useful to call out that term in the beginning, so people associate that type of job with its name and 2. another event-based job is job completion (another explicit category in the UI) and I couldn't tell how that fit into the initial description, so added that as well. Feel free to revise, just wanted to flag those two points!
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
mirnawong1
reviewed
Dec 17, 2024
mirnawong1
reviewed
Dec 17, 2024
mirnawong1
reviewed
Dec 17, 2024
mirnawong1
reviewed
Dec 17, 2024
| @@ -11,7 +11,8 @@ The job scheduler is the backbone of running jobs in dbt Cloud, bringing power a | |||
| The scheduler enables both cron-based and event-driven execution of dbt commands in the user’s data platform. Specifically, it handles: | |||
|
|
|||
| - Cron-based execution of dbt Cloud jobs that run on a predetermined cadence | |||
| - Event-driven execution of dbt Cloud CI jobs triggered by pull requests to the dbt repo | |||
| - Event-driven execution of dbt Cloud jobs that [run based on the completion of another job ([trigger on job completion](/docs/deploy/deploy-jobs#trigger-on-job-completion)) | |||
| - Event-driven execution of dbt Cloud CI jobs triggered by pull requests to the dbt repo (e.g. "merge jobs") | |||
There was a problem hiding this comment.
[custom.LatinAbbreviations] Avoid Latin abbreviations: 'for example'. Consider using 'e.g' instead.
| @@ -11,7 +11,8 @@ | |||
| The scheduler enables both cron-based and event-driven execution of dbt commands in the user’s data platform. Specifically, it handles: | |||
|
|
|||
| - Cron-based execution of dbt Cloud jobs that run on a predetermined cadence | |||
| - Event-driven execution of dbt Cloud CI jobs triggered by pull requests to the dbt repo | |||
| - Event-driven execution of dbt Cloud jobs that [run based on the completion of another job ([trigger on job completion](/docs/deploy/deploy-jobs#trigger-on-job-completion)) | |||
| - Event-driven execution of dbt Cloud CI jobs triggered by pull requests to the dbt repo (e.g. "merge jobs") | |||
There was a problem hiding this comment.
[custom.Typos] Oops there's a typo -- did you really mean 'e.g.'?
mirnawong1
approved these changes
Dec 17, 2024
There was a problem hiding this comment.
great suggestion @rcg798 ! really appreciate your contribution here and made a couple of small tweaks and merging for you!
mirnawong1
reviewed
Dec 17, 2024
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.
Coming newly into the orchestration team, I am updating the initial description of the scheduler types to better align with how users may view the product today: 1. we refer to merge jobs as merge jobs (and it is an explicit category in the UI) so I think it would be useful to call out that term in the beginning, so people associate that type of job with its name and 2. another event-based job is job completion (another explicit category in the UI) and I couldn't tell how that fit into the initial description, so added that as well. Feel free to revise, just wanted to flag those two points! If it would be easier to flag this in Slack, let me know.
What are you changing in this pull request and why?
Checklist
🚀 Deployment available! Here are the direct links to the updated files: