Scope
- Features are provided and tested for the respective milestones.
- Milestones
- TP1: Technical Preview with basic core functionality for use with shell scripts
- TP2: Technical Preview with fully featured functionality for replacement of the previous platform specific JobScheduler Agent
- RC1: Release Candidate with functionality to replace a previous standalone instance by Master/Agent instances
Test Results
- The following test results have been recorded
| Feature | Test Result TP1 | Test Result TP2 | 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 JS-1329 - Getting issue details... STATUS | |
| non-zero exit code is treated as error | | ||
| live output of log in JOC | | slow | |
| read order id with $SCHEDULER_ORDER_ID | | ||
| read job parameters as environment variables with $SCHEDULE_PARAM_ | | Works, but is case sensitive on Unix systems. Classic JobScheduler Agent works differently, seems to change all variables to upper case. | |
| read order parameters as environment variables with $SCHEDULE_PARAM_ | | Works, but is case sensitive on Unix systems. Classic JobScheduler Agent works differently, seems to change all variables to upper case. | |
| 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 JS-1300 - Getting issue details... STATUS | |
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 | | Not implemented | |
| API jobs with javascript monitor | | Not implemented | |
| spooler_init() | | ||
| spooler_open() | | ||
| spooler_process() | | ||
| spooler_close() | | not called | |
| spooler_exit() | | ||
| spooler_process_before() | | ||
| spooler_process_after() | | ||
| spooler_task_before() | | ||
| spooler_task_after() | | not called | |
| 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() | | 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 | | Most JITL jobs try to read factory.ini to establish a database connection.This causes the error sos.settings.SOSProfileSettings.load(141): java.lang.Exception: couldn't find settings-file [/home/jenkins/jobscheduler_agent_1.10-TP1/bin/C:/ProgramData/sos-berlin.com/jobscheduler/alnb_4444/config/factory.ini] There are several problems: see Discussion | |
| JobSchedulerExistsFile | | ||
Operations | |||
| add command abort to Agent start script | | ||
| command stop for Agent start script enables running processes to complete | |