geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Barrett <>
Subject Re: Failing to get resources from Maven in CI
Date Fri, 07 Dec 2018 00:16:15 GMT
Given that this seems to be an ongoing problem with bintray I think it is time we put a local
caching repository in our CI network. The native project ran into this same issue for months
at one point. Depending on where in the internet you live the bintray host you get can be
flakey. For native we would get a glacially slow server from a connections on a certain ISP.
If we put Artifactory or something on a GCP instance and proxy all Maven dependencies through
it we could cut down these issues significantly. If the artifact is already cached, nothing
to do, but it needs to fetch upstream it is really good about trying multiple sources and
retrying on transient failures.

Objections? Thoughts?


> On Dec 6, 2018, at 4:01 PM, Helena Bales <> wrote:
> Hello,
> It looks like we are still having some problems with Maven in CI. I got the
> following error in the pre-checkin for this PR
> <>
(the first commit). Since I
> didn't change any dependencies, I would expect the image to already have
> all the dependencies, and since we increased the timeout for the Maven
> connection, I would expect us to be able to connect to Maven. This issue is
> coming up frequently enough that I think we should do something about it.
> What can we do to fix this?
> Part of the error message:
>> Could not resolve
>     Required by:
>         project : >
>         project : > >
>> Could not resolve
>> Could not get resource
> ''.
>> Could not GET
> ''.
>> Connect to
> []
failed: connect timed out

View raw message