What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hey, did anybody ever set ```run_on_non_production => false``` in jobs.php? It seems to make the

UKMHZV8LX
UKMHZV8LX Posts: 69 πŸ§‘πŸ»β€πŸš€ - Cadet

Hey, did anybody ever set

run_on_non_production => false

in jobs.php?
It seems to make the job not run on production, but on any different environment. Cronjobs::getSchedule() will determine any environment different from production as production.
Do I get something wrong here?

Comments

  • sprymiker
    sprymiker Sprykee Posts: 781 πŸ§‘πŸ»β€πŸš€ - Cadet

    It does not determinate anything at the moment.

    The old scheduler module had the following logic:
    If run_on_non_production => true job runs regardless scheduler is off in config.

  • sprymiker
    sprymiker Sprykee Posts: 781 πŸ§‘πŸ»β€πŸš€ - Cadet

    In current implementation this option is ignored.

  • UKMHZV8LX
    UKMHZV8LX Posts: 69 πŸ§‘πŸ»β€πŸš€ - Cadet

    Cronjobs gets it from SetupConfig, which is deprecated, I am aware. However the behavior does not seem like intended.

  • sprymiker
    sprymiker Sprykee Posts: 781 πŸ§‘πŸ»β€πŸš€ - Cadet

    I assume this parameter is legacy and should not be relied on.