You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Helena Bales <hb...@pivotal.io> on 2018/12/07 00:01:35 UTC
Failing to get resources from Maven in CI
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
<https://github.com/apache/geode/pull/2964> (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 com.netflix.nebula:nebula-gradle-interop:0.6.0.
Required by:
project : > com.netflix.nebula:nebula-project-plugin:5.1.0
project : > com.netflix.nebula:nebula-project-plugin:5.1.0 >
com.netflix.nebula:gradle-dependency-lock-plugin:6.0.0
> Could not resolve com.netflix.nebula:nebula-gradle-interop:0.6.0.
> Could not get resource
'https://plugins.gradle.org/m2/com/netflix/nebula/nebula-gradle-interop/0.6.0/nebula-gradle-interop-0.6.0.pom'.
> Could not GET
'https://plugins.gradle.org/m2/com/netflix/nebula/nebula-gradle-interop/0.6.0/nebula-gradle-interop-0.6.0.pom'.
> Connect to jcenter.bintray.com:443
[jcenter.bintray.com/75.126.118.188] failed: connect timed out
Re: Failing to get resources from Maven in CI
Posted by Sean Goller <sg...@pivotal.io>.
I agree. We should deploy a caching server to resolve this.
On Thu, Dec 6, 2018 at 4:16 PM Jacob Barrett <jb...@pivotal.io> wrote:
> 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?
>
> -Jake
>
>
> > On Dec 6, 2018, at 4:01 PM, Helena Bales <hb...@pivotal.io> 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
> > <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_geode_pull_2964&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=dUZ47GLLeizzE2hSUiriIoTlIpvoqfbYDvZD45P2srM&m=W_6FJHVE85xyXpDMaO9yVyW-eRFIPNzpQTJjDm8KTlI&s=GjQzRsChANuUYXEnFc9LovzzIEr_s5XFmFPSU5-dQ8I&e=>
> (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 com.netflix.nebula:nebula-gradle-interop:0.6.0.
> > Required by:
> > project : > com.netflix.nebula:nebula-project-plugin:5.1.0
> > project : > com.netflix.nebula:nebula-project-plugin:5.1.0 >
> > com.netflix.nebula:gradle-dependency-lock-plugin:6.0.0
> >> Could not resolve com.netflix.nebula:nebula-gradle-interop:0.6.0.
> >> Could not get resource
> > '
> https://urldefense.proofpoint.com/v2/url?u=https-3A__plugins.gradle.org_m2_com_netflix_nebula_nebula-2Dgradle-2Dinterop_0.6.0_nebula-2Dgradle-2Dinterop-2D0.6.0.pom&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=dUZ47GLLeizzE2hSUiriIoTlIpvoqfbYDvZD45P2srM&m=W_6FJHVE85xyXpDMaO9yVyW-eRFIPNzpQTJjDm8KTlI&s=zF0AKeB_4ff6Z6vyIaQRZcISf6bZy9bVJUoYauZci-0&e=
> '.
> >> Could not GET
> > '
> https://urldefense.proofpoint.com/v2/url?u=https-3A__plugins.gradle.org_m2_com_netflix_nebula_nebula-2Dgradle-2Dinterop_0.6.0_nebula-2Dgradle-2Dinterop-2D0.6.0.pom&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=dUZ47GLLeizzE2hSUiriIoTlIpvoqfbYDvZD45P2srM&m=W_6FJHVE85xyXpDMaO9yVyW-eRFIPNzpQTJjDm8KTlI&s=zF0AKeB_4ff6Z6vyIaQRZcISf6bZy9bVJUoYauZci-0&e=
> '.
> >> Connect to
> https://urldefense.proofpoint.com/v2/url?u=http-3A__jcenter.bintray.com&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=dUZ47GLLeizzE2hSUiriIoTlIpvoqfbYDvZD45P2srM&m=W_6FJHVE85xyXpDMaO9yVyW-eRFIPNzpQTJjDm8KTlI&s=F2LvC1coGwut-9sy2cbmLeWeDafmNRiUYL458xaR_Q0&e=:443
> > [
> https://urldefense.proofpoint.com/v2/url?u=http-3A__jcenter.bintray.com_75.126.118.188&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=dUZ47GLLeizzE2hSUiriIoTlIpvoqfbYDvZD45P2srM&m=W_6FJHVE85xyXpDMaO9yVyW-eRFIPNzpQTJjDm8KTlI&s=SNOKq9weHDmT2RyQzsjfOo_Jc2MCr9vP4NuGoHOp8I8&e=]
> failed: connect timed out
>
>
Re: Failing to get resources from Maven in CI
Posted by Jacob Barrett <jb...@pivotal.io>.
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?
-Jake
> On Dec 6, 2018, at 4:01 PM, Helena Bales <hb...@pivotal.io> 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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_geode_pull_2964&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=dUZ47GLLeizzE2hSUiriIoTlIpvoqfbYDvZD45P2srM&m=W_6FJHVE85xyXpDMaO9yVyW-eRFIPNzpQTJjDm8KTlI&s=GjQzRsChANuUYXEnFc9LovzzIEr_s5XFmFPSU5-dQ8I&e=> (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 com.netflix.nebula:nebula-gradle-interop:0.6.0.
> Required by:
> project : > com.netflix.nebula:nebula-project-plugin:5.1.0
> project : > com.netflix.nebula:nebula-project-plugin:5.1.0 >
> com.netflix.nebula:gradle-dependency-lock-plugin:6.0.0
>> Could not resolve com.netflix.nebula:nebula-gradle-interop:0.6.0.
>> Could not get resource
> 'https://urldefense.proofpoint.com/v2/url?u=https-3A__plugins.gradle.org_m2_com_netflix_nebula_nebula-2Dgradle-2Dinterop_0.6.0_nebula-2Dgradle-2Dinterop-2D0.6.0.pom&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=dUZ47GLLeizzE2hSUiriIoTlIpvoqfbYDvZD45P2srM&m=W_6FJHVE85xyXpDMaO9yVyW-eRFIPNzpQTJjDm8KTlI&s=zF0AKeB_4ff6Z6vyIaQRZcISf6bZy9bVJUoYauZci-0&e='.
>> Could not GET
> 'https://urldefense.proofpoint.com/v2/url?u=https-3A__plugins.gradle.org_m2_com_netflix_nebula_nebula-2Dgradle-2Dinterop_0.6.0_nebula-2Dgradle-2Dinterop-2D0.6.0.pom&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=dUZ47GLLeizzE2hSUiriIoTlIpvoqfbYDvZD45P2srM&m=W_6FJHVE85xyXpDMaO9yVyW-eRFIPNzpQTJjDm8KTlI&s=zF0AKeB_4ff6Z6vyIaQRZcISf6bZy9bVJUoYauZci-0&e='.
>> Connect to https://urldefense.proofpoint.com/v2/url?u=http-3A__jcenter.bintray.com&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=dUZ47GLLeizzE2hSUiriIoTlIpvoqfbYDvZD45P2srM&m=W_6FJHVE85xyXpDMaO9yVyW-eRFIPNzpQTJjDm8KTlI&s=F2LvC1coGwut-9sy2cbmLeWeDafmNRiUYL458xaR_Q0&e=:443
> [https://urldefense.proofpoint.com/v2/url?u=http-3A__jcenter.bintray.com_75.126.118.188&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=dUZ47GLLeizzE2hSUiriIoTlIpvoqfbYDvZD45P2srM&m=W_6FJHVE85xyXpDMaO9yVyW-eRFIPNzpQTJjDm8KTlI&s=SNOKq9weHDmT2RyQzsjfOo_Jc2MCr9vP4NuGoHOp8I8&e=] failed: connect timed out