We are pleased to announce that Spring Cloud Task 1.1.0.M2 is now available via Github and the Pivotal download repository. Many thanks to all of those who contributed to this release.
This release continues to progress on 1.1.0’s main theme of improving overall task functionality as well as migrating features that existed within Spring XD to Spring Cloud Task. The main updates for this release are the following:
- Support for Generated Task Id - A common use case for a Spring Cloud Task application is to launch it within a PaaS, like Cloud Foundry or other cloud infrastructure. Because of this, there may be a delay between the launch request and the actual application beginning. Worse, the system responsible for launching the application may not actually launch the task for reasons outside of Spring Cloud Task’s control (lack of resources, network issues, etc). This feature allows the caller to register that a task has been requested to run. This way, no request of a task is lost between the request and the actual start of the Boot application.
- Support for External Execution Id - When executing a task on a PaaS or other cloud infrastructure, there is typically a mapping that needs to occur between the task’s execution id and the id provided by the underlying system. This feature provides the ability to correlate those two for things like log management, audit, etc.
Spring Cloud Task 1.1.0 is expected to be GA before the end of the year in line with Spring Cloud Data Flow 1.1.0. Between now and then, we’ll be adding additional capabilities to better integrate with Spring Cloud Data Flow.