: Matthieu Brouillard [mailto:matth...@brouillard.fr]
Gesendet: Freitag, 22. Januar 2021 20:14
An: Maven Developers List
Betreff: Re: uploading to central via ossrh is problematic
Markus,
> which is just one of several ways onto Maven Central
The only way for OSS developers not part of
-
> Von: Matthieu Brouillard [mailto:matth...@brouillard.fr]
> Gesendet: Freitag, 22. Januar 2021 18:36
> An: Maven Developers List
> Betreff: Re: uploading to central via ossrh is problematic
>
> Hi Romain,
>
> Thanks for the hint, I do not use the 'maven-deploy-plugin'
]
Gesendet: Freitag, 22. Januar 2021 18:36
An: Maven Developers List
Betreff: Re: uploading to central via ossrh is problematic
Hi Romain,
Thanks for the hint, I do not use the 'maven-deploy-plugin' to reach
central but I use 'nexus-staging-maven-plugin' as described on
central/sonat
Maven deploy plugin works but nexus one automates some stages (like closing
the staging and releasing it without having to do iy manually after the
upload).
Le ven. 22 janv. 2021 à 18:36, Matthieu Brouillard
a écrit :
> Hi Romain,
>
> Thanks for the hint, I do not use the 'maven-deploy-plugin' t
Hi Romain,
Thanks for the hint, I do not use the 'maven-deploy-plugin' to reach
central but I use 'nexus-staging-maven-plugin' as described on
central/sonatype documentation [1].
The issues are not coming from uploads but from internal
publication/staging inside the OSSRH infrastructure as far as
Hi
AFAIK maven enables to configure the "uploader" and even to switch it
(through wagon) so you can use any retry mecanism...but will not solve a
broken server issue, will just fail later from my experience.
Le ven. 22 janv. 2021 à 15:47, Matthieu Brouillard
a écrit :
> Hi Brian & list,
>
> Sor
Hi Brian & list,
Sorry but I have to insist on the fact that again yesterday and today OSSRH
is mostly unavailable.
I again tried, like others, to deploy artifacts and it failed.
After pinging on twitter, the OPs have provided again a feedback that
deployments have pilled [1] explaining the timeou
On 2021-01-21T13:51:36 -0500
Brian Fox wrote:
> OSSRH itself is in the
> process of being federated and large projects are given the
> opportunity to move to their own new, or separate instance so their
> load doesn't hurt the many thousands of other builds flowing through
> the system at any giv
I think that each of those other instances are more unrelated to each
other, except in some cases massive scale. OSSRH itself is in the
process of being federated and large projects are given the
opportunity to move to their own new, or separate instance so their
load doesn't hurt the many thousand
Thanks Brian,
I'll reopen an issue next time I face an upload problem.
*> it's not occurring across the entire system *
Ok but the case was not isolated, it occurred also in the past weeks to
microsoft, redhat, springboot guys and to several anonymous like me that
try to maintain some oss stuff.
Hi Matthieu, I think continuing the conversation on your existing
ossrh ticket is the right place to resolve this. While it seems like
you're having recurring issues, it's not occurring across the entire
system so we need to figure out what the unique issue is.
--Brian
Cofounder & CTO Sonatype
On
Hello,
Can a representative provide some information on the topic. Are there
discussions with Sonatype?
Yesterday again OSSRH had troubles [1].
The graphs on https://status.maven.org/ can look ok but I suspect the
99.99% of OSSRH availability to be only an HTTP health check which does not
represen
Hi all,
I know the issue/problem below is not directly related to maven dev list
but I thought it would be a good place to open the discussion.
It has been the case for several months now : community is facing issues
when deploying to central via OSSRH.
Personally I faced the issue several times,
13 matches
Mail list logo
