| Feature | Test Result
TP1 | Test Result
TP2 | Test Result
TP3 | Comment |
|---|
Core Functionality | | | | |
| execution of shell jobs |  | | | |
| stdout of shell jobs is logged as info | | | | |
| stderr of shell jobs is logged | | | | stderr is logged as info, probably related to | Jira |
|---|
| server | SOS JIRA |
|---|
| serverId | 6dc67751-9d67-34cd-985b-194a8cdc9602 |
|---|
| key | JS-1329 |
|---|
|
|
| non-zero exit code is treated as error | | | | |
| live output of log in JOC | | | | |
| read order id with $SCHEDULER_ORDER_ID | | | | |
| read job parameters as environment variables with $SCHEDULE_PARAM_ | | | | |
| read order parameters as environment variables with $SCHEDULE_PARAM_ | | | | |
| set order parameters using SCHEDULER_RETURN_VALUES | | | | |
| kill a running task |  |  | | process lost in JOC, but remote process is not killed |
| file watching | | | | incoming files trigger a job chain, see | Jira |
|---|
| server | SOS JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 6dc67751-9d67-34cd-985b-194a8cdc9602 |
|---|
| key | JS-1300 |
|---|
|
, this feature will require a JobScheduler 1.10 SNAPSHOT release as a new master functionality is used. |
JobScheduler API | | | | |
| API jobs with javascript | | | | Yes, but with API restrictions, see details below |
| API jobs with java | | | | Yes, but with API restrictions, see details below |
| Shell jobs with javascript monitor | | | | Yes, but with API restrictions, see details below |
| Shell jobs with java monitor | | | | Yes, but with API restrictions, see details below |
| API jobs with java monitor | | | | |
| API jobs with javascript monitor | | | | |
| spooler_init() | | | | |
| spooler_open() | | | | |
| spooler_process() | | | | |
| spooler_close() | | | | |
| spooler_exit() | | | | |
| spooler_process_before() | | | | |
| spooler_process_after() | | | | |
| spooler_task_before() | | | | |
| spooler_task_after() | | | | |
| spooler.create_variable_set() | | | | |
| spooler.job() | | | | |
| spooler_task.params() | | | | |
| spooler_task.order.params() | | | | |
| Variable_set.set_value() | | | | |
| Variable_set.var() | | | | |
| Variable_set.merge() | | | | |
| Variable_set.count() | | | | |
| Variable_set.substitute() | | | | |
| Variable_set.xml() | | | | |
| Variable_set.set_xml() | | | | |
| Log.info() (and all other log levels) | | | | |
| Log.filename() | | | | |
| Log.last() | | | | |
| Log.set_level() | | | | |
| Log.level() | | | | |
| Log.log_file() | | | | |
| Log.set_mail_on_error() | | | | |
| Log.set_mail_on_success() | | | | |
| Log.set_mail_on_process() | | | | |
| Log.set_mail_on_warning() | | | | |
| Log.start_new_file() |  | | | Runs on master. Rotates log on master. Agent uses log4j based logging, rotation can be configured in log4f configuration. The call to start_new_file results in COM-80020009 com.sos.scheduler.engine.minicom.types.COMException: COM-80020009 , method=call |
| Job.set_delay_after_error(int,double) | | | | |
| Job.set_delay_after_error(int,String) | | | | |
| Job.clear_delay_after_error() | | | | |
| Job.set_delay_order_after_setback(int, double) | | | | |
| Job.set_delay_order_after_setback(int, String) | | | | |
| Job.max_order_setbacks() | | | | |
| Job.set_max_order_setbacks() | | | | |
| Job.configuration_directory() | | | | |
| Job.folder_path() | | | | |
| Job.include_path() | | | | |
| Job.name() | | | | |
| Job.process_class() | | | | |
| Job.remove() | | | | |
JITL Jobs | | | | |
File Operations | | | | |
| JobSchedulerExistsFile | | | | |
| JobSchedulerCanWrite | | | | |
| JobSchedulerCopyFile | | | | |
| JobSchedulerMoveFile | | | | |
| JobSchedulerRemoveFile | | | | |
Job Handling | | | | |
| JSReportAllParameters | | | | |
| CopyJob2OrderParameter | | | not | job is currently not working correctly, unrelated to the agent, see | Jira |
|---|
| server | SOS JIRA |
|---|
| serverId | 6dc67751-9d67-34cd-985b-194a8cdc9602 |
|---|
| key | JITL-179 |
|---|
|
tested |
| JobChainSplitter | | | | not tested |
| JobSchedulerCheckRunHistory | | | | has to be migrated, needs database settings |
Maintenance | | | | |
| JobSchedulerCleanupFiles | | | | runs on master and on agent |
| JobSchedulerDatabaseMonitor | | | | runs on master, needs database connection properties from factory.ini |
| JobSchedulerMailBounceHandler | | | | runs on master, needs settings from factory.ini |
| AgentBatchInstaller | | | | installs old agent, must be migrated to a job that installs the new agent |
| CheckDailySchedule | | | | runs on master |
| JSObjects2Graphviz | | | | runs on master, works with live folder |
| JobSchedulerCheckEvents |  | | | not tested - does not make sense on agent, should run on master |
| JobSchedulerCheckExistEvents | | | | not tested - does not make sense on agent, should run on master |
Operations | | | | |
| add command abort to Agent start script | | | | see | Jira |
|---|
| server | SOS JIRA |
|---|
| serverId | 6dc67751-9d67-34cd-985b-194a8cdc9602 |
|---|
| key | JS-1400 |
|---|
|
|
| command stop for Agent start script enables running processes to complete | | | | see | Jira |
|---|
| server | SOS JIRA |
|---|
| serverId | 6dc67751-9d67-34cd-985b-194a8cdc9602 |
|---|
| key | JS-1400 |
|---|
|
|