Search
Page 50 of 93. Showing 930 results (0.012 seconds)
callback2.pl
are identified with the following format: # -- # # complete-job-first # # in the callback we are setting up, the plan is to unblock # the second job. # # to do this we will use…Email Notification
Jobs can be setup to automatically e-mail the job's owner when the job has completed. This is enabled on a job per job basis. A job is also allowed to e-mail a user besides…Event Model
. For a complete explanation on how Qube allows jobs to modify the logic surrounding the job, please reference the Callbacks section of the documentation. Migrated to Confluence 5.3…Email Notification
Jobs can be setup to automatically e-mail the job's owner when the job has completed. This is enabled on a job per job basis. A job is also allowed to e-mail a user besides…Event Model
. For a complete explanation on how Qube allows jobs to modify the logic surrounding the job, please reference the Callbacks section of the documentation. Migrated to Confluence 5.3…Event Model
. For a complete explanation on how Qube allows jobs to modify the logic surrounding the job, please reference the Callbacks section of the documentation. Migrated to Confluence 5.3…_worker_bootstrap_parameter
in the worker's local qb.conf configuration file. Any mention in the global qbwrk.conf file will be ignored. This is a complete list of the Worker bootstrap parameters…qb_calc_status($subjob, $agenda)
and $agenda status information (these are strings like "complete", "killed", and "failed"), the function is allowed to calculate what the job's overall status value…_worker_bootstrap_parameter
in the worker's local qb.conf configuration file. Any mention in the global qbwrk.conf file will be ignored. This is a complete list of the Worker bootstrap parameters…qb_calc_status($subjob, $agenda)
and $agenda status information (these are strings like "complete", "killed", and "failed"), the function is allowed to calculate what the job's overall status value…