From d54072e0a83f7878fc1db56bbee3325f0353e3ba Mon Sep 17 00:00:00 2001 From: Andy Wilkinson Date: Mon, 4 Jun 2018 16:39:06 +0100 Subject: [PATCH] More accurately document buildInfo's effect on up-to-date checking Closes gh-13152 --- .../src/main/asciidoc/integrating-with-actuator.adoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/main/asciidoc/integrating-with-actuator.adoc b/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/main/asciidoc/integrating-with-actuator.adoc index 434b2dbaf99..cf140e1dca5 100644 --- a/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/main/asciidoc/integrating-with-actuator.adoc +++ b/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/main/asciidoc/integrating-with-actuator.adoc @@ -51,11 +51,11 @@ include::../gradle/integrating-with-actuator/build-info-custom-values.gradle[tag ---- The default value for `build.time` is the instant at which the project is being built. A -side-effect of this is that the task will never be up-to-date and, therefore, builds will -take slightly longer as more tasks will have to be executed. Another side-effect is that -the task's output will always change and, therefore, the build will not be truly -repeatable. If you value build performance or repeatability more highly than the accuracy -of the `build.time` property, set `time` to `null` or a fixed value. +side-effect of this is that the task will never be up-to-date. As a result, builds will +take longer as more tasks, including the project's tests, will have to be executed. +Another side-effect is that the task's output will always change and, therefore, the build +will not be truly repeatable. If you value build performance or repeatability more highly +than the accuracy of the `build.time` property, set `time` to `null` or a fixed value. Additional properties can also be added to the build information: