From 1e6c29c1af658d8fb04aded8b140f17e0342b61f Mon Sep 17 00:00:00 2001 From: Hyeonmin Park Date: Mon, 28 Nov 2022 00:22:26 +0900 Subject: [PATCH] Add init scripts file name guide for build scan capturing Signed-off-by: Hyeonmin Park --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 5404efb..b033e54 100644 --- a/README.md +++ b/README.md @@ -384,6 +384,13 @@ jobs: }) ``` +Note that the build scan capturing utilizes the [Initialization Script](https://docs.gradle.org/current/userguide/init_scripts.html#sec:using_an_init_script) +in the `USER_HOME/.gradle/init.d/` directory, with the file named `build-result-capture.init.gradle`. +So, if you are using the init scripts for the [Gradle Enterprise Gradle Plugin](https://plugins.gradle.org/plugin/com.gradle.enterprise) like +[`scans-init.gradle` or `gradle-enterprise-init.gradle`](https://docs.gradle.com/enterprise/gradle-plugin/#scans_gradle_com), +make sure that its file names have earlier alphabetical order to the `build-result-capture.init.gradle`, +since configuring capture requires Gradle Enterprise Gradle Plugin to be applied already. + ## Support for GitHub Enterprise Server (GHES) You can use the `gradle-build-action` on GitHub Enterprise Server, and benefit from the improved integration with Gradle. Depending on the version of GHES you are running, certain features may be limited: