www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Bouron"<tbou...@apache.org>
Subject Re: Failed to deploy artifacts: Could not transfer artifact xxxx to/from apache.shapshots.https
Date Thu, 19 Oct 2017 12:42:13 GMT

We do experience the same behaviour for Brooklyn project, at about the same rate.
Latest failure being this build: https://builds.apache.org/job/brooklyn-library-master/463

As Marshall pointed out, rerunning the build fixes the issue in most cases.

Any idea what might cause this?

On 2017-10-12 14:25, 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

View raw message