xF2 Add-on CLI Job Runner 1.5.0

v1.5.0 makes some back-end changes to the way we manage the lock files and fixes an issue where long running jobs could see multiple job runners executing at the same time

• code cleanup: we don't need a custom app class to show jobs
• new CLI command: hg:show-crons
• new CLI command: hg:run-cron
• add logQuiet function to LoggerTrait
• rebuilt Lock functionality to use a non-static class, managed by a SubContainer
• ensure lock expiry is at least 30 seconds after the max execution time (10 minutes)

v1.4.2 simply adds a check for the installer to prevent installation on XenForo 2.2 - need to install v2 of the JobRunner addon for XF 2.2 compatibility.

There is no need for existing users of this addon running on XenForo v2.1 to upgrade to v1.4.2

remove redundant class extension thanks to XF 2.2b2

Click to expand...

New features:

• implemented debug logger for Job execution time tracking
• extend the XF\Job\Cron class with new run function which logs execution time for cron tasks
• added new Cli command and test job for testing purposes

Thanks to @Xon for identifying the bug fix where AJAX JSON responses would still trigger job.php; and for making suggestions on avoiding unnecessary database queries and prevent running cron jobs unless triggered via our CLI job runner

• changes: disable calculations for job auto run time to avoid unnecessary database queries
• bug fix: disable AJAX auto job runner from triggering from AJAX JSON responses
• changes: don't allow cron tasks to execute unless triggered via the CLI job runner

• changes: new icon
• bug fix: should return 0 for successful execution
• new feature: show-jobs command

Minor update for XF2.0 and now tested on XF2.1

• we still want to run jobs if the user has disabled version checking in config
• clear entity cache each time we run a job, to keep memory usage under control

Same version, new addon_id.

If you already have v1.0.0 installed, there is no need to upgrade. There is no new functionality in v1.0.0a. New installations should use this v1.0.0a version to ensure compatibility with future releases.

Due to the change in addon_id, upgrading from v1.0.0 to v1.0.0a is not supported - but there is no data stored with this addon, so simply uninstalling v1.0.0 before installing v1.0.0a will be sufficient.