From da30e4c444604351316126aaf315d72a47b71604 Mon Sep 17 00:00:00 2001
From: Michael Keppler <michael.keppler@gmx.de>
Date: Tue, 10 Dec 2024 08:01:38 +0000
Subject: [PATCH] Authentication times out very quickly

---
 readme.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/readme.md b/readme.md
index d328b89..98ea9e1 100644
--- a/readme.md
+++ b/readme.md
@@ -291,6 +291,9 @@ In order to authenticate a local development machine, Develocity offers automate
 
 When executed, the automated provisioning launches a web browser to [develocity-staging.eclipse.org](https://develocity-staging.eclipse.org/) and asks you to sign in. All Eclipse Foundation committers can log in using their Eclipse account: email / password.
 
+Be aware that the develocity Maven plugin waits only a very short time for the browser process to finish the authentication.
+If you get a Socket timeout or similar in the Maven console, just repeat the command and confirm more quickly in the browser.
+
 #### Unauthenticated Builds
 
 Builds that are not authenticated to Develocity will simply not publish a Build Scan®. A lack of authentication will not cause the build to fail and will not be shown to the user. This includes builds by unauthenticated Eclipse committers, unauthenticated CI systems, or community contributors.
-- 
GitLab