Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Maven Central connection resets

Hi

Thanks for clarifying Sonatype/OSSRH.

But what about a local M2E build (on my workstation)? I appear to have no ~/.m2/settings.xml and so no mirror configuration. Since I'm in Europe (UK), [1] suggests that I should have a mirror.

    Regards

        Ed Willink


[1] https://maven.apache.org/guides/mini/guide-mirror-settings.html


On 30/07/2018 13:13, Christoph Daniel Schulze wrote:
Ed,

the ELK project publishes some of its compiled libraries as Maven
artifacts. Doing so includes pushing those artifacts to Sonatype's
servers (OSSRH refers to those same servers), which then distribute them
to be available through Maven Central. It's a bit of a mess regarding
the names...

Builds that do not publish to Sonatype servers are fine since they rely
on ~/.m2/settings.xml, where the Maven Central mirror is correctly
configured.

Builds that do publish to Sonatype servers need credentials to do so
securely. Those credentials are provided in a separate settings.xml file
which is used instead of ~/.m2/settings.xml and -- this is the problem
-- did not include the Maven Central mirror configuration.

The way I understand it, everything is fine as long as you don't have a
build that pushes to Maven Central, and even those builds are fixed as
we speak, according to Frederic's mail below.

Cheers,
 Chris

On 30.07.18 14:05, Ed Willink wrote:
Hi

Could you please clarify?Sonatype/OSSRJ mean nothing to me.

Is the standard Jenkins / HIPP ok, or is that what you are fixing?

Is some action needed for a local Tycho build? Perhaps it was on a local
rather than Jenkins build that I observed very slow Maven connections.

    Regards

        Ed Willink


On 30/07/2018 11:45, Frederic Gurr wrote:
Hi,

FYI:
We will add the missing Maven Central mirror to all existing Maven
settings files that are used for deployment to OSSRH.

Regards,

Fred

On 30.07.2018 12:30, Christoph Daniel Schulze wrote:
Hi,

just to wrap this up: the problem seems to have been solved solved by
adding the Maven Central mirror to our custom settings file. Thanks for
the idea of looking at our settings file, Ed -- I must have missed that
while reading through the comments on bug 492412.

Cheers,
 Chris

On 30.07.18 11:21, Christoph Daniel Schulze wrote:
Hi Ed,

according to [1] the proxy doesn't seem to be necessary anymore.

I've been running the cat command as well. Indeed, the mirror is defined
in our settings file as well, but the Jenkins settings specify a
different settings file in order for us to be able to publish Maven
artifacts to the Sonatype servers. I'll check with the administrators
whether this setting causes ~/.m2/settings.xml to not be loaded.

Cheers,
 Chris

[1] https://wiki.eclipse.org/Jenkins#Proxies

On 30.07.18 11:09, Ed Willink wrote:
Hi

I just tried the cat ${HOME}/.m2/settings.xml on the OCL HIPP and it
differs from David's result:

+2 additonal server declarations
=1 same mirror declation
-1 proxy declaration

Perhaps the missing proxy is a concern.

    Regards

        Ed Willink


On 30/07/2018 09:19, Christoph Daniel Schulze wrote:
Hi Ed,

well, it's out nightly build, I don't really want to try it later. Also,
as it is now, it fails 100% of the time.

I just stumbled upon bug 492412 [1], which is about a mirror of Maven
Central. Should that mirror be used by default? Because that does not
seem to be the case in our build.

Cheers,
 Chris

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=492412

On 28.07.18 22:02, Ed Willink wrote:
Hi

Yes, I have regular build fails. Trying again later works eventually,
probably because each attempt completes a few downloads till there is
nothing left to fetch.

If you look at the log in detail you will see that the transfer rate for
some successful downloads is only a few KB/s suggesting that the problem
is probably at the Maven end. I guess that such pathetic transfer rates
can vary a bit and when the rate drops it is a failure. Perhaps there is
a tomeout that Eclipse IT can set to be more tolerant.

    Regards

        Ed Willink



On 28/07/2018 20:02, Christoph Daniel Schulze wrote:
Hello everyone,

we (the ELK project) are having lots of trouble with our automatic build
at the moment [1]. The problems used to be limited to connection
problems while publishing artifacts to Sonatype. By now, we cannot get a
single build to complete due to problems downloading plug-ins from Maven
Central.

In short, here's the problem:

Downloading from central:
http://central.maven.org/maven2/com/google/code/gson/gson/maven-metadata.xml
[WARNING] Could not transfer metadata
com.google.code.gson:gson/maven-metadata.xml from/to central
(http://central.maven.org/maven2): Connection reset

Sure enough, the file does exist on the server.

Have other projects seen similar issues? If so, how did you solve them?

Cheers,
 Chris

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=537325



_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
	Virus-free. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev


_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev


_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev


      

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev


Back to the top