Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Feature
- Environment variables should be propagated to SSH sessions. This applies to environment variables
- globally for JobScheduler, e.g. $SCHEDULER_HOST, $SCHEDULER_TCP_PORT etc.
- individually for tasks, e.g. SCHEDULER_TASK_ID, SCHEDULER_JOB_NAME, job parameters
Implications
- JobScheduler can be configured to prefix environment variables for job parameters and order parameters.
- The JobScheduler variable scheduler.variable_name_prefix is used to determine a possible prefix.
- The JITL SSH job respects this setting and creates prefixes accordingly.
- The JITL SSH job will
- propagate task parameters first and then order parameters which includes a higher precedence of order parameters.
- JobScheduler global environment variables and task specific environment variables are used from the JVM environment.
Note
- The SSH job comes in 1.9 with two different implementations (JSch and Trilead).
- This ticket works only with JSch which will be the default implementation since 1.10. In 1.9 is Trilead the default.
- To activate JSch in 1.9 you have to configure the ./config/scheduler.xml with the following parameter:
<param name="jitl.ssh.use_jsch_impl" value="true"/>