www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: Failed to deploy artifacts: Could not transfer artifact xxxx to/from apache.shapshots.https
Date Thu, 19 Oct 2017 13:34:40 GMT
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
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message