And rename it to '--force' if you don't want to check the rules.

Comments

gielfeldt’s picture

I'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.

gielfeldt’s picture

Issue summary: View changes
Status: Active » Postponed
gielfeldt’s picture

Status: Postponed » Fixed

The --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.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.