[FOLIO-2262] Jenkins maven builds fail, trouble with repository.folio.org maven-public Created: 16/Sep/19 Updated: 03/Jun/20 Resolved: 16/Sep/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | David Crossley | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | devops, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | CP: sprint 72 |
| Story Points: | 3 |
| Development Team: | Core: Platform |
| Description |
|
Today Jenkins maven-based builds are failing today. It appears to be trouble getting artifacts from our "maven-public" Nexus. |
| Comments |
| Comment by David Crossley [ 16/Sep/19 ] |
|
Output snippet: ... [INFO] Scanning for projects... [INFO] Downloading: https://repository.folio.org/repository/maven-public/org/jacoco/jacoco-maven-plugin/maven-metadata.xml [INFO] Downloaded: https://repository.folio.org/repository/maven-public/org/jacoco/jacoco-maven-plugin/maven-metadata.xml (0 B at 0.0 KB/sec) [WARNING] The metadata /home/jenkins/.m2/repository/org/jacoco/jacoco-maven-plugin/maven-metadata-folio-nexus.xml is invalid: input contained no data [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1.363 s [INFO] Finished at: 2019-09-16T06:48:52+00:00 [INFO] Final Memory: 10M/342M [INFO] ------------------------------------------------------------------------ [INFO] [jenkins-event-spy] Generated /home/jenkins/workspace/ta-import_folio-2235-ld-settings@tmp/withMaven6251c542/maven-spy-20190916-064850-4721331256621494675695.log [ERROR] Error resolving version for plugin 'org.jacoco:jacoco-maven-plugin' from the repositories [local (/home/jenkins/.m2/repository), folio-nexus (https://repository.folio.org/repository/maven-public)]: Plugin not found in any plugin repository ... |
| Comment by John Malconian [ 16/Sep/19 ] |
|
The issue appears to be related to the jitpack maven repo. The jacoco-maven-plugin appears to be available in both Maven Central and JitPack, however, the Nexus proxy is choosing Jitpack and Jitpack's repo contains invalid data. I've removed Jitpack from the proxy and the plugin is picked up from Maven Central correctly. Only mod-circulation uses the Jitpack repo, so I would expect build failures there until this is resolved. |
| Comment by John Malconian [ 16/Sep/19 ] |
|
There is an artifact required by mod-circulation that is only provided by the jitpack.io maven repo. However, for some reason, Nexus was unable to proxy the artifacts correctly, perhaps because of some recent change by jitpack.io. In the end, I removed jitpack.io from the list of proxied maven repositories in Nexus and modified the global maven settings file that Jenkins uses to fetch artifacts directly from jitpack.io instead of the nexus proxy. |