- Due to the lack of multipage Html support we need to revert to Docbook for the time being
- Revert "gh-246 Remove docbooks from asciidoctor infrastructure"
- This reverts commit 4ed50a6b31.
The Spring build infrastructure has the capabilities to deploy
documentation automatically that it finds in Artifactory. This commit
creates the required zip archive for that process.
Resolves SCT-78
resolves#115
* Fixes bug where if the user set the environment variable and commandline args a unique constraint would fire.
* Updated docs
* Removed deprecation
* Fixed version number for integration test.
Added integration tests for externally generated task executions
Add externalExecutionId
resolves#80
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.
Resolvesspring-cloud/spring-cloud-task#186
Disabled integration tests by default
Just some cleanup on merge
Created a Spring Boot starter that can be used to configure Spring Cloud
Task and it's related functionality.
Updates per code review
Removed autowiring of app context
Refactored DeployerPartitionHandler to correctly use environment variables
Exposed deployment properties of TaskLauncher
Exposed deployment properties via the TaskLaunchRequest
Updated based on code review
Versions where updated in documentation that is included in the
generation of our reference documentation.
Also, to clean up version management within the samples, the
spring-cloud-task-dependencies was introduced into each pom so that
versions are managed at that level.
Updated a version number
Adds a Task Listener that emits the TaskExecution as an event via a
Spring Cloud Stream channel (essentially the listener serves as a SCSt
Source).
Resolvesspring-cloud/spring-cloud-task#11
In testing and other use cases, the ability to keep a context open
beyond the end of a task can be useful. This change provides the
ability to keep the context alive once a task has completed while also
explicitly shutting the context down (by default) once a task has ended.
Resolvesspring-cloud/spring-cloud-task#102
DeployerStepExecutionHandler
Created a PartitionHandler that delegates to a TaskLauncher from Spring
Cloud Deployer to execute workers.
Resolvesspring-cloud/spring-cloud-task#109
Updates per code review
This commit changes the starting point of a task from the point when the
ApplicationContext issues the ContextRefreshedEvent to
SmartLifecycle#start. This is a more accurate point of start for a task
in that all beans should now be available. It also allows us to clean
up many ApplicationContext hacks that were present to get around the
fact that many beans were not ready when a Task was attempting to begin.
Resolvesspring-cloud/spring-cloud-task#107
Added the ability to implement TaskExecutionListener functionality without
implementing the TaskExecutionListener interface.
resolvesspring-cloud/spring-cloud-task#95
TaskLifecycleListener will set a TaskExecution's exitCode to null upon taskStart in the repository.
Only at the end of the execution will it store the exitCode.
resolvesspring-cloud/spring-cloud-task#82
This is the initial cut of the reference documentation for Spring Cloud
Task.
Resolvesspring-cloud/spring-cloud-task#49
Updates per code review
use mvnw instead of mvn in example
