Mark Maven build failures as configuration errors

github · Mar 14, 2024 · 88a0b7a · 88a0b7a
1 parent 88b28eb
commit 88a0b7a
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 1 deletion.
diff --git a/lib/cli-errors.js b/lib/cli-errors.js
diff --git a/lib/cli-errors.js.map b/lib/cli-errors.js.map
diff --git a/src/cli-errors.ts b/src/cli-errors.ts
@@ -124,6 +124,7 @@ export enum CliConfigErrorCategory {
   IncompatibleWithActionVersion = "IncompatibleWithActionVersion",
   InitCalledTwice = "InitCalledTwice",
   InvalidSourceRoot = "InvalidSourceRoot",
+  MavenBuildFailed = "MavenBuildFailed",
   NoBuildCommandAutodetected = "NoBuildCommandAutodetected",
   NoBuildMethodAutodetected = "NoBuildMethodAutodetected",
   NoSourceCodeSeen = "NoSourceCodeSeen",
@@ -164,6 +165,11 @@ export const cliErrorsConfig: Record<
   [CliConfigErrorCategory.InvalidSourceRoot]: {
     cliErrorMessageCandidates: [new RegExp("Invalid source root")],
   },
+  [CliConfigErrorCategory.MavenBuildFailed]: {
+    cliErrorMessageCandidates: [
+      new RegExp("[autobuild] [ERROR] Failed to execute goal"),
+    ],
+  },
   [CliConfigErrorCategory.NoBuildCommandAutodetected]: {
     cliErrorMessageCandidates: [
       new RegExp("Could not auto-detect a suitable build method"),