Skip to content
Snippets Groups Projects
Select Git revision
  • e362b6159cff7a724159aeba2df154bc87623607
  • main default protected
  • register-logging-channel
  • expr-lang
  • ci-82
  • attr-events
  • locale-wip
  • custom-routes
  • v0.1.85
  • v0.1.84
  • v0.1.83
  • v0.1.82
  • v0.1.81
  • v0.1.80
  • v0.1.79
  • v0.1.78
  • v0.1.77
  • v0.1.76
  • v0.1.75
  • v0.1.74
  • v0.1.73
  • v0.1.72
  • v0.1.71
  • v0.1.70
  • v0.1.69
  • v0.1.68
  • v0.1.67
  • v0.1.65
28 results

CronTest.php

  • Reiter, Christoph's avatar
    e362b615
    cron: don't run all jobs if there was no previous run · e362b615
    Reiter, Christoph authored
    In case the API is started the first time, or it is re-deployed
    and the cache is cleared/removed the API doesn't know when the
    cron jobs were last checked.
    
    Up until now it would assume that the last run was so long ago that
    all jobs are due and run all jobs. This has the downside that on
    a re-deploy all jobs are run, despite most of them not needing to.
    
    This changes the defaults to not run any jobs if there is no previous
    check recorded.
    
    If the admin still wants to force run all jobs there is the "--force"
    option that can be passed to the cron command.
    e362b615
    History
    cron: don't run all jobs if there was no previous run
    Reiter, Christoph authored
    In case the API is started the first time, or it is re-deployed
    and the cache is cleared/removed the API doesn't know when the
    cron jobs were last checked.
    
    Up until now it would assume that the last run was so long ago that
    all jobs are due and run all jobs. This has the downside that on
    a re-deploy all jobs are run, despite most of them not needing to.
    
    This changes the defaults to not run any jobs if there is no previous
    check recorded.
    
    If the admin still wants to force run all jobs there is the "--force"
    option that can be passed to the cron command.