Skip to content

Job system

The job system enables automating tasks implemented as a command.

It is based on the JMSJobQueueBundle.

You can see an overview of the last jobs in the Back Office by clicking Control Center > e-commerce jobs.

Expand a running job to see more details of its state. You can see the output of the command.

The list is automatically updated every 10 seconds.

You can add your own jobs to the menu. The user can then click Start and the job is executed.

Starting jobs

The job system requires executing the jms-job-queue:run command (see Required crontab tasks).

1
php bin/console jms-job-queue:run --env=prod

A job can be started using the Back Office (and a configuration of tasks offered) or using the PHP API.

See bundle documentation for more details about the PHP API.

Configuring jobs for the Back Office

You can configure project-specific jobs which are displayed in the Back Office.

You can define the Symfony command (parameter command) and the parameters.

If your job requires additional tasks, you can add these tasks in the depending_jobs parameter. These jobs are started after the main job has been executed successfully.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
parameters:
    siso_control_center.default.add_jobs:
        import_solr:
            label: "Import from eZ"
            desc: "Starts import from a remote system"
            command: "silver:import"
            params:
                - tmp
            depending_jobs:
                index_solr:
                    label: "Index econtent tmp cores"
                    command: "ibexa:commerce:index-econtent-job"

Removing old jobs

To remove old jobs, run the following command:

1
bin/console jms-job-queue:clean-up --env=prod --per-call=10 --max-retention="1 min"