Closed (fixed)
Project:
Ultimate Cron
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
17 Jun 2013 at 08:55 UTC
Updated:
28 Mar 2014 at 12:01 UTC
Jump to comment: Most recent
Comments
Comment #1
gielfeldt commentedI've been thinking about this. The way it works now, is that it mimics the actions in the interface, e.g. "run all" will run the scheduled jobs, "run" on a single job will run the job regardless of its schedule.
The use-case for Drush is similar I believe. When you perform a "drush cron-run all", it's because you want to run the scheduled jobs. When you run "drush cron-run ", it's because you want to run that job now.
There's a slight problem though. When using the --cli option, you need the --check-rule to actually make Ultimate Cron double check the "catch up" in the sub-requests.
I think I'll address this in 2.x somehow instead, if it turns out to be a problem there.
Comment #2
gielfeldt commentedComment #3
gielfeldt commentedThe --cli option has been removed, as this is now the launchers responsibility.
The --check-rule has been renamed to --check-schedule as per the new terminology in Ultimate Cron. The boolean logic, however, remains the same. Defaults to schedule checking for all jobs and no schedule checking for a single job.
Please reopen ticket if you disagree.