From 394498f89f091edf93b65ecf9e74f5b517b69fdb Mon Sep 17 00:00:00 2001
From: Daz DeBoer <daz@gradle.com>
Date: Mon, 26 Sep 2022 10:57:52 -0600
Subject: [PATCH] Avoid appending to existing build-results file

When configuration-cache is enabled, the invocationId may not be unique, which can result in
mulitple builds writing to the same file. Rather than failing the post-action, we simply
ignore any subsequent build results with the same ID.

Fixes #441
---
 .../init-scripts/build-result-capture-service.plugin.groovy   | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/resources/init-scripts/build-result-capture-service.plugin.groovy b/src/resources/init-scripts/build-result-capture-service.plugin.groovy
index 8eaf7fa..68bd380 100644
--- a/src/resources/init-scripts/build-result-capture-service.plugin.groovy
+++ b/src/resources/init-scripts/build-result-capture-service.plugin.groovy
@@ -54,6 +54,8 @@ abstract class BuildResultsRecorder implements BuildService<BuildResultsRecorder
         def buildResultsDir = new File(runnerTempDir, ".build-results")
         buildResultsDir.mkdirs()
         def buildResultsFile = new File(buildResultsDir, githubActionStep + getParameters().getInvocationId().get() + ".json")
-        buildResultsFile << groovy.json.JsonOutput.toJson(buildResults)
+        if (!buildResultsFile.exists()) {
+            buildResultsFile << groovy.json.JsonOutput.toJson(buildResults)
+        }
     }
 }