-
Notifications
You must be signed in to change notification settings - Fork 2.5k
SystemCommandTasklet does not propagate errors #4483
Copy link
Copy link
Closed
Labels
for: backport-to-5.0.xIssues that will be back-ported to the 5.0.x lineIssues that will be back-ported to the 5.0.x linefor: backport-to-5.1.xIssues that will be back-ported to the 5.1.x lineIssues that will be back-ported to the 5.1.x linehas: minimal-exampleBug reports that provide a minimal complete reproducible exampleBug reports that provide a minimal complete reproducible examplein: coretype: bug
Milestone
Metadata
Metadata
Assignees
Labels
for: backport-to-5.0.xIssues that will be back-ported to the 5.0.x lineIssues that will be back-ported to the 5.0.x linefor: backport-to-5.1.xIssues that will be back-ported to the 5.1.x lineIssues that will be back-ported to the 5.1.x linehas: minimal-exampleBug reports that provide a minimal complete reproducible exampleBug reports that provide a minimal complete reproducible examplein: coretype: bug
Type
Fields
Give feedbackNo fields configured for issues without a type.
SystemCommandTaskletdoes not propagate errorsIf a command executed by
SystemCommandTaskletreturns a non zero exit code, the system exit code is mapped to ExitStatus.FAILED. However, the overall step execution status is BatchStatus.COMPLETED, meaning the step (and the job) is completed successfully.Environment
spring-batch 5.0.3
Steps to reproduce
Create a Job with a
SystemCommandTaskletwhere the system command executed will return a non zero exit code.Expected behavior
The error should be propagated to the Step, and ultimately to the overall Job execution status.