- Feature: Added "on_success" csl of job codes that will be scheduled after the job completed successfully.
- Fix: #305 Reduce lock waiting/deadlock potential by using
READ COMMITTEDtransaction isolation level. - Fix: #305 Use atomic status updates where appropriate and save
STATUS_SKIP_*status after setting. RemovedSTATUS_SKIP_LOCKED.
- Feature: #273: Add memory usage column to scheduler list (Thanks, @steverobbins!)
- Feature: Added new shell commands
--enableJoband--disableJob - Feature: Added cache prefix check (see description here)
- and some other minor bugfixes,...
- Feature: Added bumper-to-bumper feature (status: "repeat") for always tasks
- Fix: #117/#199 Fixed duplicate schedules at the time of schedule generation (Thank you, @dorrogeray/@nemphys)
- Feature: #210: Make a difference between missed and skipped jobs (Thank you, @ajpevers)
- Feature: #211: Add relevant titles to scheduler admin pages (Thank you, @steverobbins)
- Fix: #213: Fatal Error: Can't use method return value in write context
- Fix: #214: Cannot filter List View by "running"
- Feature: #189: force user. (Thank you, @robbieaverill)
- Fix: #198: abstract.php not found
- Feature: Added
--forceand--tryLockto runNow from cli. This allows you to bypass checking if another instance of that task is already running and start a new one. (Only do this if you know what you're doing...)
- Fix: Died jobs does not get cleaned (#146)
- Fix: Lock identifiers in scheduler_cron.php might be wrong (Thanks, @Caprico85 and @minimax59)
- Even more robust process management:
- Now no job should ever disappear without you being able to track what happened. Using
register_shutdown_function(), 'pcntl_signal()` and the custom php error logs introduced in 1.1 you should be able to detect- if a job died because of a PHP fatal error
- if there was a hidden
exitordiein the job implementation that would have resulted in the scheduler to stop without saving the status - if the script stopped because of the memory_limit
- if the process was killed from outside (using CTRL+C or
kill <pid>. Please note thatkill -9 <pid>can not be detected!)
- Now no job should ever disappear without you being able to track what happened. Using
- More robust process management:
- Prevent all tasks to be cleaned up immediately if
system/cron/mark_as_error_afterwas set to 0 - Check if task is alive before marking it disappeared
- Add message if job was killed because of
system/cron/max_job_runtime
- Prevent all tasks to be cleaned up immediately if
- Fixed Instructions: When using
scheduler_cron.sh(instead ofcron.sh) you need to configure the default and always job in two seperate lines since we're not doing any ugly launching-processes-in-the-background there. The instructions were wrong before suggesting thatscheduler_cron.shonly without any parameters would be a sufficient configuration. But this would lead to the always tasks never being executed.
- Error Log: New configuration options were introduced that allow you to enable a per-job error-log that will be written to
var/log/cron/<jobCode>_<jobId>.log. Also you can specifiy the error level (defaults to '-1' which might be a little too verbose for many use cases). This will bypass Magento'smageCoreErrorHandlerthat would hide some errors. Please note that currently the files in var/log/cron will not be automatically deleted (even if the corresponding job is deleted). Until this feature will be added please use log rotation or other scripts to prevent that directory from growing. The filename and the prefix can be configured. - New states: Introduced
Aoe_Scheduler_Model_Schedule::STATUS_SKIP_LOCKEDandAoe_Scheduler_Model_Schedule::STATUS_SKIP_OTHERJOBRUNNINGfor more fine-grained information why a job wasn't run. Also the grid and timeline view will now show these skipped jobs. - Bugfix: Timeline view didn't render if jobs had been executed via
php scheduler.php --action runNow --code <jobCode>
This is a major release of Aoe_Scheduler. Many things have been added and improved. Please take some time to verify everything is still working as expected after updated.
- task_records overlays: In case you used the experimental task_records branch from GitHub please note that any "database overlays" you might have created will be deleted, since these database overlays are now being stored in a different way. If you don't know what this is about you can safely ignore this note :)
- Manage cron groups via environment variables: Previously it was possible to configure cron groups by defining environment variables with blacklists and whitelists. While this worked it wasn't a very elegant solution and had some issues. With the this new release of Aoe_Scheduler the processing of cron groups was rewritten from scratch and controlling the groups via environment variables was removed. If you were using this feature please go back and revisit your cron configuration. Please checkout the new instructions interface, the cron configuration page and the information on cron groups in the documentation.
- Disabling jobs: By default Magento doesn't support disabling individual cron jobs. This feature was introduced in an early version of Aoe_Scheduler and the information on what jobs are disabled was stored in a comma-separated list in the system configuration. With the now database overlays this way of storing the status was removed and migrated to the new database overleys instead. While there's a data migration script in place that should take care of the conversion I suggest double checking the list of crons to make sure jobs you disabled before are still disabled after updating.
- Major code cleanup: While previous versions of Aoe_Scheduler tried to stick as close of possible to the native implementation in
Mage_Cronthis has changed now. Aoe_Scheduler introduces a separate domain model that structures the code a lot better and allows adding new features in a much cleaner way. At the same time everything is still compatible to the natvieMage_cronmodule. If you decide to uninstall Aoe_Schedulers your jobs will continue to be executed by Magento. - Clean vocabulary: In the interface and in the code base there was some confusing on what the different terms actually are. There was 'job', 'schedule', 'task', 'run'. Now there's only 'jobs' and 'schedules'. Check out the documentation for some more details.
- Cron groups: See note above in the 'important' section.
- scheduler_cron.sh: In order to implement cron groups and other features in a cleaner way a new script was introduced:
scheduler_cron.sh. Use this instead ofcron.phporcron.sh. - Database overlays: This is probably the biggest addition to the new Aoe_Scheduler. Behind the scenes Magento was already doing this to some degree, but - as so often - this was not clearly documented and exposed to the developers. Job definitions now can not only live in XML but also be definied in the database. You can edit existing jobs (the database records can override XML jobs) e.g. disabled them, add some parameters or change settings like the schedule or you can create new jobs from scratch via the Magento admin without writing a single line of XML.
- Process management: Aoe_Scheduler is now keeping track of pids and hostnames of schedules allowing you to actually check if a schedule is still running and to actively kill it in case you need this job to stop (e.g. before deploying a new build,...)
- Documentation: Still work in progress, but we're getting there... :)
- Tests: Some integration tests are added.
- Schedule meta-data: Aoe_Scheduler now records who triggered a schedule and why (Aoe_Scheduler_Model_Schedule::REASON_*)
- Travis CI: Some basic build and CS checks: https://travis-ci.org/AOEpeople/Aoe_Scheduler
- Message buffer: Contribution from Mike Weerdenburg. Thank you!
- Job descriptions and titles: Contribution from Matthias Zeis, Thank you!
- Bugfixes and other contributions: Thanks, Robin Fritze, Nicolai Essig, Chernjie, Jason Evans! (and maybe some other! I'm sorry if I missed you here. Let me know and I'll add you to the list!)