Allows failed batch apps to set exit code of task app.

resolves #201
 Please enter the commit message for your changes. Lines starting

Cleanup Removed taskProperties from TaskBatchAutoConfiguration
This commit is contained in:
Glenn Renfro
2018-01-22 10:53:36 -05:00
committed by Michael Minella
parent b6f6d68385
commit cd4dbe6a93
12 changed files with 870 additions and 13 deletions

View File

@@ -243,8 +243,15 @@ is covered in detail in the section
As discussed before Spring Cloud Task applications support the ability to record the exit code of a task execution.
However in cases where a user is running a Spring Batch Job within a task, regardless of how the Batch Job
Execution completes the result of the task will always be zero when using default Batch/Boot behavior. Keep in mind
that a task is a boot application and the exit code returned from the task is the same as a boot application. So
to have your task return the exit code based on the result of the batch job execution, you will need to write your
own CommandLineRunner.
Execution completes the result of the task will always be zero when using default Batch/Boot behavior.
Keep in mind that a task is a boot application and the exit code returned from
the task is the same as a boot application.
To override this behavior and allow the task to return an exit code other than zero
(either 1 `the default` or based on the
https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-spring-application.html#boot-features-application-exit[ExitCodeGenerator]
specified) upon a batch job returning an
https://docs.spring.io/spring-batch/4.0.x/reference/html/step.html#conditionalFlow[ExitStatus]
of "FAILED", set `spring.cloud.task.batch.commandLineRunnerEnabled` to true.
To have your task return the exit code based on the result of the batch job
execution, you will need to write your own `CommandLineRunner`.