Introduced Error Message to Task Execution
To provide the ability to control task orchestration via the exit message, we moved the stack trace storage to a new field. This means that exit message is now a field we can use similar to how exit code is in batch, and still have the stack trace of an unsuccessful task execution stored. Resolves spring-cloud/spring-cloud-task#186 Disabled integration tests by default Just some cleanup on merge
This commit is contained in:
committed by
Glenn Renfro
parent
551a4bc53a
commit
db0565b7cf
@@ -79,9 +79,12 @@ assumed to be 0.
|
||||
|The time the task was completed as indicated by the `ApplicationReadyEvent`.
|
||||
|
||||
|`exitMessage`
|
||||
|Any information available at the time of exit. If an exception is the cause of the end
|
||||
of the task (as indicated via an `ApplicationFailedEvent`), the stack trace for that
|
||||
exception will be stored here.
|
||||
|Any information available at the time of exit. This can programatically be set via a
|
||||
`TaskExecutionListener`.
|
||||
|
||||
|`errorMessage`
|
||||
|If an exception is the cause of the end of the task (as indicated via an
|
||||
`ApplicationFailedEvent`), the stack trace for that exception will be stored here.
|
||||
|
||||
|`arguments`
|
||||
|A `List` of the string command line arguments as they were passed into the executable boot
|
||||
|
||||
Reference in New Issue
Block a user