, August 01, 2008 2:54 PM
To: Maven Developers List
Subject: Re: Latency of syncs in Nexus with central
Brian E. Fox wrote:
>> Yep, I checked the crontab, it's actually running at 12:05 (CST) daily. I'll
>> still add the proxy.
>
> Yep, it's all set now. The inten
Brian E. Fox wrote:
Yep, I checked the crontab, it's actually running at 12:05 (CST) daily. I'll
still add the proxy.
Yep, it's all set now. The intent was to minimize traffic over to central since
we had the mirror, but we can do both and it won't hurt anything.
Hm, is the proxy setup rea
st
Subject: Re: Latency of syncs in Nexus with central
Brian E. Fox wrote:
> Yep, I checked the crontab, it's actually running at 12:05 (CST) daily. I'll
> still add the proxy.
OK, waiting a day (at most) isn't a major issue, not much things are
that urgent that a commit ca
Brian E. Fox wrote:
Yep, I checked the crontab, it's actually running at 12:05 (CST) daily. I'll
still add the proxy.
OK, waiting a day (at most) isn't a major issue, not much things are
that urgent that a commit can't wait, you only need to know. But if
Hudson gets a real-time proxy to cen
Tamás Cservenák wrote:
Central is _not_ proxied by Nexus, but is rsynced from repo1.maven.org
to repository.sonatype.org, and it is served from there by Nexus as
"hosted" repo. The problem is probably our rsync process (not [yet]
fired, or something).
Not that this solves your failed build, jus
Latency of syncs in Nexus with central
Hi there,
The problem is more how is central repo in public group on our Nexus served:
Central is _not_ proxied by Nexus, but is rsynced from repo1.maven.org
to repository.sonatype.org, and it is served from there by Nexus as
"hosted" repo. The pro
Hi there,
The problem is more how is central repo in public group on our Nexus served:
Central is _not_ proxied by Nexus, but is rsynced from repo1.maven.org
to repository.sonatype.org, and it is served from there by Nexus as
"hosted" repo. The problem is probably our rsync process (not [yet]
fir
loper List
Subject: Latency of syncs in Nexus with central
Hi,
does the Nexus instance serving our Hudson have a certain latency with
regard to catching up with central? I am wondering since CI failed [0]
on maven-invoker which I updated to use the just released
plexus-utils:1.5.6 [1]
Ben
Hi,
does the Nexus instance serving our Hudson have a certain latency with
regard to catching up with central? I am wondering since CI failed [0]
on maven-invoker which I updated to use the just released
plexus-utils:1.5.6 [1]
Benjamin
[0]
https://ci.sonatype.org/job/maven-shared/185/org
