Major Builds seem to fail if the mirror of a "Unpack *.zip/*.tar.gz Archive" Maven installation procedure is offline even though that same installation is already present.
We configured a Maven installation procedure for Maven 3.2.3 via download from one of the mirrors (see error.log.txt). Maven had been successfully installed and used since a couple of weeks ago. Last weekend builds using that Maven version started to fail with the attached output (see error.log.txt). I checked and found out that the mirror was unreachable.
However, since the installation had been successful weeks ago, the builds should not fail and use the already present installation. It should only fail on new build nodes which did not yet install the version.
- is related to
-
JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request
-
- Open
-
[JENKINS-24932] Build fails if mirror of "unpack archive" Maven installation procedure is unreachable
Do you have /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.3 path on lab76 ?
Yes. As stated in the description Maven 3.2.3 had been successfully installed and used for a couple of weeks. The installation directory had not been touched by anyone.
It just happened again. Apparently, after the 3.2.5 release of Maven, some of the 3.2.3 download mirrors went offline which causes all those jobs configured to use 3.2.3 to fail EVEN THOUGH 3.2.3 is already installed on the respective nodes.
The installation procedure should ideally only execute if the installation is not already present AND more importantly NOT fail builds; or at least only if there is no installation and downloads fail etc.
There'll be a robustness improvement (1fcee97d2fdda236fea149f671d9c8a95cdb8528) in 1.597 for JENKINS-26196. I'm resolving this as fixed for now. If you still experience this problem with Jenkins 1.597 or higher, please reopen or file a new issue.
This is probably caused by a failure in the up-to-date check used in this installer type.