[MarioPym]

Summary

On large instances, it is sometimes necessary to prevent a specific background job class from executing (for example, if a job consumes too many resources or is already handled by an external process) without disabling the app that registered it. Currently, the only workaround is deleting the job from oc_jobs, which causes the app to re-register it upon the next upgrade or app activation.

This change introduces the excluded_jobs system configuration key, which accepts a list of job class names. JobList::getNext() skips any jobs matching these classes, preventing them from being picked up by cron, webcron, AJAX, or occ background-job:worker. The jobs remain registered in the database and can still be triggered manually via occ background-job:execute. Leading backslashes in class names are supported, and the new key has been documented in config.sample.php.

How to test

1. occ config:system:set excluded_jobs 0 --value='OCA\Files\BackgroundJob\DeleteOrphanedItems'
2. Make that job due (e.g. set its last_run and last_checked to 0 in oc_jobs) and run php cron.php.
   • Before: the job runs.
   • After: the job is skipped; the rest of the jobs run as usual.
3. occ config:system:delete excluded_jobs and run cron again: the job runs.

Unit tests: tests/lib/BackgroundJob/JobListTest.php.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI