From 24aa10a1de28238fdd08a68f53ccc0fdb806d8a8 Mon Sep 17 00:00:00 2001
From: Arnout Engelen <arnout@bzzt.net>
Date: Fri, 20 Dec 2024 13:03:56 +0100
Subject: [PATCH] Try Maven Central before hitting `repository.apache.org`

We have noticed some builds causing many 404 errors on
`repository.apache.org`, causing GitHub Actions runners
to be banned (https://infra.apache.org/infra-ban.html).

Looking at various logs, it looks like this workflow
may be one of the jobs triggering this problem. Including
Maven Central explicitly in the repositories section will
make Maven check that repository first, which should help
a lot.
---
 .ci/jenkins/tests/pom.xml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/.ci/jenkins/tests/pom.xml b/.ci/jenkins/tests/pom.xml
index 450fb053a7d..be3ec557f43 100644
--- a/.ci/jenkins/tests/pom.xml
+++ b/.ci/jenkins/tests/pom.xml
@@ -27,6 +27,14 @@
     <packaging>jar</packaging>
 
     <repositories>
+        <repository>
+            <snapshots>
+                <enabled>false</enabled>
+            </snapshots>
+            <id>central</id>
+            <name>Central Repository</name>
+            <url>https://repo.maven.apache.org/maven2</url>
+        </repository>
         <repository>
             <id>apache-public-repository-group</id>
             <name>Apache Public Repository Group</name>