Wait for specified jobs to complete before starting this job (comma-separated)
Image Removed
. Click 'Add' to create
dependant
dependent jobs.
you
Image Added
You can link jobs
states
to each other
by
in several
factors
ways:
"complete" means only start this job after designated job completes
"failed" means only start this job if the designated job fails
"killed" means only start this job if the job has been killed
"done" means start this job if the job is killed/failed/complete
Email (job complete)
Tooltip -
Send email on job completion (success or failure)
Info
Info
. Sends mail to the designated userbased on the status of the job being complete .
Email (failed frames)
Tooltip - Send email on job completion (success or failure)
Sends mail to the designated user based on the status of the job being failed if frames fail.
Blocked
Tooltip -
Set initial state of job to "blocked"
Info
Enable this tickbox to ensure after submission this job is in a blocked state. You would do this if you wanted to set up other jobs for this one to depend on.
Stderr->Stdout
Tooltip -
Redirect and consolidate the job stderr stream to the stdout stream
Info
. Enable this if you would like to combine you your logs into one stream.
Job Label
Tooltip -
Optional label to identify the job. Must be
a
unique within a Job Process Group (pgrp).
Info
Legacy This is a legacy method of labelling labeling jobssee . See Job Tags
Job Kind
Tooltip -
Arbitrary typing information that can be used to identify the job.
Common usage: it can be
It is commonly used to
restrict
make sure only
1
oneof this "kind" of job
from running
runs on a worker at the same time by setting the job\'s requirements to include "not (job.kind in host.duty.kind)"
Job Process Group (pgrp) for logically organizing dependent jobs. Defaults to the jobid. Combination of "label" and "Process Group" (pgrp) must be unique for a job.