93301[FEATURE] Introduce scheduler task priority
Commit message
Review
-
Code review CR +2 Done
- Garvin Hicking +2
- Josua Vogel +1
-
Verified V +2 Done
- Garvin Hicking +2
- Josua Vogel +1
- core-ci +1 CI
Issues 1
Files 8
- typo3/sysext/core/Documentation/Changelog/14.2/Feature-109110-IntroduceSchedulerTaskPriority.rstnew+72 −0
- typo3/sysext/scheduler/Classes/Domain/Repository/SchedulerTaskRepository.php2+23 −1
- typo3/sysext/scheduler/Classes/Service/TaskService.php+1 −1
- typo3/sysext/scheduler/Configuration/TCA/tx_scheduler_task.php2+14 −0
- typo3/sysext/scheduler/Resources/Private/Language/locallang_tca.xlf+12 −0
- typo3/sysext/scheduler/Resources/Private/Partials/TaskList.fluid.html2+1 −0
- typo3/sysext/scheduler/Tests/Functional/Domain/Repository/SchedulerTaskRepositoryTest.phpnew+67 −0
- typo3/sysext/scheduler/Tests/Functional/Fixtures/FindNextExecutableTask.csvnew+6 −0
Review log 1317
-
Sebastian Michaelsen uploaded patch set 1 03/21/26, 21:56
-
core-ci voted on patch set 1 V -1 03/21/26, 22:10 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/98361
-
Sebastian Michaelsen uploaded patch set 2
V -103/21/26, 22:12 -
core-ci voted on patch set 2 V +1 03/21/26, 22:21 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/98362
-
Garvin Hicking commented on patch set 2 03/22/26, 06:35
I think this pragmatic approach could cover use cases. A solution that generates/calculates more complex execution orders (based on before/after definitions) would raise complexity a lot. Maybe this patch would for the future allow to create parallel "scheduler pipes", so one run for high prio tasks (every minute) and a low prio scheduler (every hour).SchedulerTaskRepository.php:537We should utilize TCA Schema API heretx_scheduler_task.php:73For new fields we should use the "scheduler.tca:tx_scheduler_task.priority" label notation (also below)TaskList.fluid.html:265Maybe to prevent the table that already spans too wide with a new cell, and add priority below frequency as an information? Maybe even with an info pill layout?ext_tables.sql:4Theoretically this could be auto-created, did you test as what it gets created? Numbers would be good so extensions could add their own numbers via TCA Override -
Sebastian Michaelsen uploaded patch set 3
V +103/22/26, 09:05 -
Sebastian Michaelsen commented on patch set 2 03/22/26, 09:05
SchedulerTaskRepository.php:537ReplyDonetx_scheduler_task.php:73ReplyDoneTaskList.fluid.html:265ReplyDoneext_tables.sql:4ReplyDone -
core-ci voted on patch set 3 V +1 03/22/26, 09:15 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/98378
-
Garvin Hicking voted on patch set 3 CR +1 03/22/26, 11:07
-
Benni Mack commented on patch set 3 03/22/26, 15:52
scheduler_file_storage_extraction_task.php:50hey, I Have an idea, let's move the execution_details, next_execution, and last_execution into one palette (in a prepatch). then we can just add priority to all fields -
Sebastian Michaelsen uploaded patch set 4
CR +1V +103/23/26, 10:00 -
Sebastian Michaelsen commented on patch set 4 03/23/26, 10:00
scheduler_file_storage_extraction_task.php:50ReplyDone -
core-ci voted on patch set 4 V +1 03/23/26, 10:39 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/98446
-
Garvin Hicking voted on patch set 4 CR +1 V +1 03/23/26, 11:19
-
Josua Vogel voted on patch set 4 CR +1 V +1 03/23/26, 11:46
-
Garvin Hicking voted on patch set 4 CR +2 V +2 03/24/26, 07:02
-
Garvin Hicking merged patch set 5 03/24/26, 07:02