You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/data-sources/job.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,8 +27,18 @@ description: |-
27
27
-`description` (String) Long description for the job
28
28
-`environment_id` (Number) ID of the environment the job is in
29
29
-`id` (String) The ID of this resource.
30
+
-`job_completion_trigger_condition` (Set of Object) Which other job should trigger this job when it finishes, and on which conditions. (see [below for nested schema](#nestedatt--job_completion_trigger_condition))
30
31
-`name` (String) Given name for the job
31
32
-`self_deferring` (Boolean) Whether this job defers on a previous run of itself (overrides value in deferring_job_id)
32
33
-`timeout_seconds` (Number) Number of seconds before the job times out
33
34
-`triggers` (Map of Boolean) Flags for which types of triggers to use, keys of github_webhook, git_provider_webhook, schedule, custom_branch_only
34
35
-`triggers_on_draft_pr` (Boolean) Whether the CI job should be automatically triggered on draft PRs
Copy file name to clipboardExpand all lines: docs/resources/job.md
+47-3Lines changed: 47 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,13 @@ description: |-
13
13
Those improvements include modifications to deferral which was historically set at the job level and will now be set at the environment level.
14
14
Deferral can still be set to "self" by setting `self_deferring` to `true` but with the new approach, deferral to other runs need to be done with `deferring_environment_id` instead of `deferring_job_id`.
15
15
16
+
17
+
~> As of beginning of February 2024, job chaining with `job_completion_trigger_condition` is in private beta and not available to all users.
18
+
<br/>
19
+
<br/>
20
+
This notice will be removed once the feature is generally available.
-`execute_steps` (List of String) List of commands to execute for the job
83
117
-`name` (String) Job name
84
118
-`project_id` (Number) Project ID to create the job in
85
-
-`triggers` (Map of Boolean) Flags for which types of triggers to use, possible values are `github_webhook`, `git_provider_webhook`, `schedule` and `custom_branch_only`. <br>`custom_branch_only` is only relevant for CI jobs triggered automatically on PR creation to only trigger a job on a PR to the custom branch of the environment.
119
+
-`triggers` (Map of Boolean) Flags for which types of triggers to use, possible values are `github_webhook`, `git_provider_webhook`, `schedule` and `custom_branch_only`. <br>`custom_branch_only` is only relevant for CI jobs triggered automatically on PR creation to only trigger a job on a PR to the custom branch of the environment. To create a job in a 'deactivated' state, set all to `false`.
-`deferring_job_id` (Number) Job identifier that this job defers to (legacy deferring approach)
92
126
-`description` (String) Description for the job
93
127
-`generate_docs` (Boolean) Flag for whether the job should generate documentation
94
-
-`is_active` (Boolean) Flag for whether the job is marked active or deleted
128
+
-`is_active` (Boolean) Flag for whether the job is marked active or deleted. To create/keep a job in a 'deactivated' state, check the `triggers` config.
129
+
-`job_completion_trigger_condition` (Block Set, Max: 1) Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining'). (see [below for nested schema](#nestedblock--job_completion_trigger_condition))
95
130
-`num_threads` (Number) Number of threads to use in the job
96
-
-`run_generate_sources` (Boolean) Flag for whether the job should run generate sources
131
+
-`run_generate_sources` (Boolean) Flag for whether the job should add a `dbt source freshness` step to the job. The difference between manually adding a step with `dbt source freshness` in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run.
97
132
-`schedule_cron` (String) Custom cron expression for schedule
98
133
-`schedule_days` (List of Number) List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
99
134
-`schedule_hours` (List of Number) List of hours to execute the job at if running on a schedule
0 commit comments