www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin <marti...@apache.org>
Subject Re: Failed to deploy artifacts: Could not transfer artifact xxxx to/from apache.shapshots.https
Date Sat, 21 Oct 2017 14:04:02 GMT
Hi,

we have the same problem here on the archiva builds, but use our own archiva repository url:
Failed to transfer file: https://archiva-repository.apache.org/archiva/repository/snapshots/org/apache/archiva/archiva-indexer/3.0.0-SNAPSHOT/maven-metadata.xml.
Return code is: 400, ReasonPhrase: Bad Request.

Is there some component like a loadbalancer or reverse proxy that limits the number of requests
per client, or resets requests after some timeout?

Greetings

Martin

Am Donnerstag, 19. Oktober 2017, 15:34:40 CEST schrieb Gary Gregory:
> FYI: We seen the same errors for Log4j 2.
> 
> Gary
> 
> On Oct 12, 2017 07:26, "Marshall Schor" <msa@schor.com> wrote:
> 
> > Hi,
> >
> > We are getting failing builds where the build itself succeeds, but a
> > subsequent
> > failure happens at the post-build step of transferring artifacts to
> > apache.snapshots.  Many of the artifacts get transferred, but then an
> > error pops
> > up:
> >
> > ERROR: Failed to deploy artifacts: Could not transfer artifact xxxx
> > from/to apache.snapshots.https (https://repository.apache.
> > org/content/repositories/snapshots): Failed to transfer file: yyyy.
> > Return code is: 400, ReasonPhrase: Bad Request.
> >
> > These failures are intermittent, perhaps 30% of the build trys.
> >
> > Rerunning the jenkins job often succeeds.
> >
> > Here's an example of a recent failure:
> > https://builds.apache.org/job/UIMA-v3-sdk/279/display/
> > redirect?page=changes
> >
> > Can we change something to improve the odds of having deployment work?
> >
> > -Marshall Schor
> >
> >
> 



Mime
View raw message