Spring Cloud Task 2.2.1 GA is now available

Engineering
Glenn Renfro
November 25, 2019

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

translate：
翻译：

Spring Cloud Task 2.2.1.RELEASE旨在成为与Spring Boot 2.2.x保持一致的框架版本。此新版本中的更新包括：

更新所有依赖项。
千分尺支持。
更新了具有改进格式的文档。
现在，使用Spring Batch分区启动时启动的任务应用已填充了external-execution-id。

让我们更详细地了解这些更新。
更新到所有依赖项

如前所述，此版本使Spring Cloud Task与Spring Boot 2.2.x保持一致。这包括更新所有依赖项。
千分尺支持

可将基于Spring Cloud Task 2.2.0版本构建的Task应用程序配置为向Micrometer支持的预配置监视系统发出Task和Batch指标。特定于任务的指标包括任务持续时间和任务执行状态。您可以在此处阅读有关此新功能的更多信息。如果您还没有听说过Micrometer，它为最流行的监视系统提供了一个基于仪表客户端的简单外观，使您无需供应商锁定即可对基于JVM的应用程序代码进行仪表。你可以在这里读更多关于它的内容。
更新了具有改进格式的文档

为了提高Spring Cloud Task参考文档的可读性和实用性，我们花了一些时间来更新文档的格式和语法。其中一些更改包括页面左侧的参考链接，这些链接可用于快速访问关键主题以及一种使文档更具可读性的新样式。他们可以在这里找到。让我们知道您的想法！
现在，在使用分区时启动的任务应用已填充了外部执行ID

Spring Cloud Task现在捕获平台为每个分区任务启动提供的执行ID，并将其存储为该分区的任务执行记录的一部分。 （您可以将外部执行ID视为PID（如果在本地系统上启动任务，则可以将其视为PID）。这使您可以使用平台的工具来搜索应用程序中的问题，从而诊断应用程序的问题它提供的ID。
你怎么看？