ChainedType vs SimpleTask #87
-
|
What is the advantage of using a chained task rather than a simple task list ? For example: // chained type
tasks:
chained:
type: 'chained'
single_run: true
description: 'chained tasks'
output: true
output_to_store: true
tasks:
command1:
type: 'command'
command: 'app:command1'
command2:
type: 'command'
command: 'app:command2'
command3:
type: 'command'
command: 'app:command3'
command4:
type: 'command'
command: 'app:command4'VS // simple FiFO tasks
tasks:
command1:
type: 'command'
command: 'app:command1'
single_run: true
command2:
type: 'command'
command: 'app:command2'
single_run: true
command3:
type: 'command'
command: 'app:command3'
single_run: true
command4:
type: 'command'
command: 'app:command4'
single_run: trueThis configuration has the advantage of giving information task by task, which is not found on a chained task. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Don't get the point here, could you be more precise?
Actually, that's just a limitation on the display, not on the implementation, the goal that I have in mind is to display the informations of each embedded tasks when using the command: php bin/console scheduler:list
chained task
> sub-task
> sub-task |
Beta Was this translation helpful? Give feedback.
-
for example when consulting the entrypoint {
"code": 200,
"tasks": [
{
"body": {
"tasks": [
{
"body": {
"command": "app:command1",
"arguments": [],
"options": [],
"name": "command1",
"arrival_time": null,
"before_scheduling": null,
"before_scheduling_notification_bag": null,
"after_scheduling_notification_bag": null,
"before_executing_notification_bag": null,
"after_executing_notification_bag": null,
"after_scheduling": null,
"before_executing": null,
"after_executing": null,
"description": null,
"expression": "* * * * *",
"execution_absolute_deadline": null,
"execution_computation_time": null,
"execution_delay": null,
"execution_memory_usage": null,
"execution_period": null,
"execution_relative_deadline": null,
"execution_start_date": null,
"execution_end_date": null,
"execution_start_time": null,
"execution_end_time": null,
"last_execution": null,
"max_duration": null,
"max_executions": null,
"max_retries": null,
"nice": null,
"state": "enabled",
"execution_state": "succeed",
"output": false,
"priority": 0,
"queued": false,
"scheduled_at": null,
"single_run": false,
"tags": [],
"timezone": null,
"tracked": true
},
"taskInternalType": "SchedulerBundle\\Task\\CommandTask"
},
{
"body": {
"command": "app:command2",
"arguments": [],
"options": [],
"name": "command2",
"arrival_time": null,
"before_scheduling": null,
"before_scheduling_notification_bag": null,
"after_scheduling_notification_bag": null,
"before_executing_notification_bag": null,
"after_executing_notification_bag": null,
"after_scheduling": null,
"before_executing": null,
"after_executing": null,
"description": null,
"expression": "* * * * *",
"execution_absolute_deadline": null,
"execution_computation_time": null,
"execution_delay": null,
"execution_memory_usage": null,
"execution_period": null,
"execution_relative_deadline": null,
"execution_start_date": null,
"execution_end_date": null,
"execution_start_time": null,
"execution_end_time": null,
"last_execution": null,
"max_duration": null,
"max_executions": null,
"max_retries": null,
"nice": null,
"state": "enabled",
"execution_state": "succeed",
"output": false,
"priority": 0,
"queued": false,
"scheduled_at": null,
"single_run": false,
"tags": [],
"timezone": null,
"tracked": true
},
"taskInternalType": "SchedulerBundle\\Task\\CommandTask"
},
],
"name": "chained",
"arrival_time": "2021-04-29T08:15:02+00:00",
"before_scheduling": null,
"before_scheduling_notification_bag": null,
"after_scheduling_notification_bag": null,
"before_executing_notification_bag": null,
"after_executing_notification_bag": null,
"after_scheduling": null,
"before_executing": null,
"after_executing": null,
"description": "deploy single_run command",
"expression": "* * * * *",
"execution_absolute_deadline": null,
"execution_computation_time": 19093579,
"execution_delay": null,
"execution_memory_usage": 6487882832,
"execution_period": null,
"execution_relative_deadline": null,
"execution_start_date": null,
"execution_end_date": null,
"execution_start_time": "2021-04-29T08:15:02+00:00",
"execution_end_time": "2021-04-29T13:33:15+00:00",
"last_execution": "2021-04-29T13:33:15+00:00",
"max_duration": null,
"max_executions": null,
"max_retries": null,
"nice": null,
"state": "paused",
"execution_state": "succeed",
"output": true,
"priority": 0,
"queued": false,
"scheduled_at": "2021-04-29T07:16:12+00:00",
"single_run": true,
"tags": [
"deploy"
],
"timezone": "UTC",
"tracked": true
},
"taskInternalType": "SchedulerBundle\\Task\\ChainedTask"
}
]
} |
Beta Was this translation helpful? Give feedback.
-
|
This limitation is due to the execution of Issue: #77 |
Beta Was this translation helpful? Give feedback.
-
|
yes I see well, indeed when it will be implemented we will find the information. But in this case what advantage does one or the other solution bring |
Beta Was this translation helpful? Give feedback.
-
|
By default, tasks cannot be grouped for now outside of |
Beta Was this translation helpful? Give feedback.
Don't get the point here, could you be more precise?
Actually, that's just a limitation on the display, not on the implementation, the goal that I have in mind is to display the informations of each embedded tasks when using the command: