From 91983b025667cd72aba97087ce43ba571f10aa71 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ole=20Sch=C3=B6nburg?= <ole.schoenburg@gmail.com>
Date: Tue, 9 May 2023 15:46:32 +0200
Subject: [PATCH] ci: update snapshots and retry download of released artifacts

---
 .github/actions/setup-zeebe/action.yml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/.github/actions/setup-zeebe/action.yml b/.github/actions/setup-zeebe/action.yml
index 54c366d9f19a..9951021b8755 100644
--- a/.github/actions/setup-zeebe/action.yml
+++ b/.github/actions/setup-zeebe/action.yml
@@ -93,6 +93,9 @@ runs:
       shell: bash
       # `--errors` ensures errors will also spit out a stack trace, which is always useful, and has no impact on normal builds
       #
+      # `--update-snapshots` to force Maven into updating snapshots, but also to retry looking for
+      #    release artifacts when an earlier lookup failure made it into the cache.
+      #
       # `maven.wagon.*` and `maven.resolver.transport` set the resolver's network transport to Wagon,
       #    the old provider pre 3.9. Until Maven 3.9.2, we have to do this if we want to retry on
       #    network issues, as otherwise any issue will fail the build.
@@ -105,6 +108,7 @@ runs:
         tee .mvn/maven.config <<EOF
         --errors
         --batch-mode
+        --update-snapshots
         -D maven.wagon.httpconnectionManager.ttlSeconds=120
         -D maven.wagon.http.pool=false
         -D maven.resolver.transport=wagon