> - full repair and md5 checksums of geoserver snapshots: 25 mins >> - A quick task to rebuild maven-metadata.xml just for the org.geotools.* >> snapshots, taking 1:23 >> >> *Travis retry:* [WARNING] The POM for >> org.geotools.ogc:net.opengis.ows:jar:25-SNAPSHOT is missing, no dependency >> information available >> - so just the org.geotools.* snapshots does not cut it, changing to clean >> up all in geotools-snapshot >> > > Clean up what exactly? The Travis build itself keeps a cache of the local > maven repo, but removes > all GT/GWC/GS jars before the caching happens: > https://github.com/geoserver/geoserver/blob/master/.travis.yml#L38 >
I made a "repair" activity on repo.osgeo.org geotools snapshots repository, just repairing org.geotools.* jars did not work, since we have some with the net.opengis.* pattern. Our difficult is the repository being messed up, we currently cannot tell if that is due to either multiple concurrent builds deploying at the same time, or scheduled activities that "clean up" older snapshot jars. > > I'm wondering about the maven repository hosting... does it have any form > of safety, like rate limiting and the like, > that might trigger when the multiple builds we have all start in parallel > and download jars from the repo? > It could be in the repo manager, but also in whatever is fronting it on > its way to the internet. > I have reopened https://trac.osgeo.org/osgeo/ticket/2502, and added your question as a comment.
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
