a monitor to notify of system events
The job is received.
The job is received. Do something with it and reply...
the originating http request
the unmarshalled input process
the eventual HttpResponse
Here additional parameters are given to aid in potential subclassing
Here additional parameters are given to aid in potential subclassing
the unique job id
the directory the job is running in
the input request
the job unmarshalled from the http request
the loggers used in the running job
the future of the exit code
an HttpResposne
the workspaces to use in determining/awaiting working directories
Executes the 'RunProcess' using the given 'defaultEnv' (default system properties), workspace, and input request.
The workflow is:
1) await any dependencies declared on the RunProcess using the WorkspaceClient 2) upon success of #1, a ProcessLoggers is created for the job in the working directory using the MatchDetails extracted from the HttpRequest headers (if any). Any std out or std err files from the RunProcess are appended to the ProcessLoggers used to run the job. 3) An HttpResponse future is prepared based on the HttpRequest given. That response will either be a FileResult if no streaming settings are provided or a StreamingResult if result streaming was specified by the RunProcess.output.stream.
Note: if any std out or std err files were specified, then the WorkspaceClient.triggerUploadCheck will be invoked to re-check any files which may depend on the output
the HttpResponse in a future