Engineering
Releases
News and Events

Spring Cloud Task 2.2.1 GA is now available

We are pleased to announce that the Spring Cloud Task 2.2.1.RELEASE is now available on Github and the Pivotal download repository. Many thanks to all of those who contributed to this release.

What’s New?

The Spring Cloud Task 2.2.1.RELEASE is intended to be the version of the framework aligned with Spring Boot 2.2.x. Updates in this new version include:

  • Update all dependencies.
  • Micrometer support.
  • Updated documentation with improved format.
  • Task apps launched when using Spring Batch partitioning now have external-execution-id populated.

Let’s walk through these updates in more detail.

Update to All Dependencies

As stated earlier, this release brings Spring Cloud Task into alignment with Spring Boot 2.2.x. This includes updating all dependencies.

Micrometer Support

Task applications built on the Spring Cloud Task 2.2.0 version can be configured to emit Task and Batch metrics to the pre-configured monitoring systems supported by Micrometer. The task-specific metrics include task duration and task execution status. You can read more about this new feature here. If you have not heard about Micrometer, it provides a simple facade over the instrumentation clients for the most popular monitoring systems, letting you instrument your JVM-based application code without vendor lock-in. You can read more about it here.

Updated Documentation with Improved Format

To improve the readability and usefulness of the Spring Cloud Task reference documentation, we have spent some time updating the format and syntax of the documentation. Some of these changes include reference links on the left hand side of page for quick access to key topics as well as a new style to make the docs more readable. They can be found here. Let us know what you think!

Task Apps Launched When Using Partitioning Now Have external-execution-id Populated

Spring Cloud Task now captures the execution ID provided by the platform for each partitioned task launch and stores that as a part of the task execution record for that partition. (You can think of an external execution ID as the PID (and is the PID if you launch your task on your local system). This lets you use the platform’s tools to diagnose issues with your apps by being able to search the platform for the ID it provided.

What Do You Think?

We look forward to your feedback on these new features in Github, on StackOverflow, Gitter, or directly via Twitter to @michaelminella or @cppwfs!

Spring Cloud Task Home | Source on GitHub | Reference Documentation

comments powered by Disqus