
|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
0.5d
|
|
|
Remaining Estimate:
|
0.25d
|
|
|
Time Spent:
|
0.25d
|
|
|
|
|
A common use case for the job level ExecutionContext was to allow a file that was generated from one step as output, to be used as input in another step. However, the StepExecutionResourceProxy can't pull values from the job level execution context, which would require the value to be moved over.
|
|
Description
|
A common use case for the job level ExecutionContext was to allow a file that was generated from one step as output, to be used as input in another step. However, the StepExecutionResourceProxy can't pull values from the job level execution context, which would require the value to be moved over. |
Show » |
|
It seems like this issue should be resolved in the 1.1 branch as well? The primary use case for the Job level ExecutionContext was to use a file created in one step as the input for another step.