You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2017/10/12 13:25:46 UTC
Failed to deploy artifacts: Could not transfer artifact xxxx to/from
apache.shapshots.https
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
Re: Failed to deploy artifacts: Could not transfer artifact xxxx
to/from apache.shapshots.https
Posted by Marshall Schor <ms...@schor.com>.
I posted "works for me" now to Jira. If any of the other projects are still
having this issue, please speak up on the Jira
https://issues.apache.org/jira/browse/INFRA-15366
-Marshall
On 10/12/2017 9:25 AM, Marshall Schor 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
>
>
Re: Failed to deploy artifacts: Could not transfer artifact xxxx to/from apache.shapshots.https
Posted by Thomas Bouron <tb...@apache.org>.
Hi.
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 <ms...@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
>
>
Fwd: Re: Failed to deploy artifacts: Could not transfer artifact xxxx
to/from apache.shapshots.https
Posted by Marshall Schor <ms...@schor.com>.
meant to copy our dev list on this... Filed an Infra Jira for this.
-Marshall
-------- Forwarded Message --------
Subject: Re: Failed to deploy artifacts: Could not transfer artifact xxxx
to/from apache.shapshots.https
Date: Tue, 24 Oct 2017 16:26:04 -0400
From: Marshall Schor <ms...@schor.com>
To: builds@apache.org
The frequency of failure seems to have increased, at least for one of our builds
- it is now mostly failing (after uploading many of the artifacts to the snapshot).
Filed a Jira https://issues.apache.org/jira/browse/INFRA-15366 . -Marshall
On 10/21/2017 10:04 AM, Martin wrote:
> 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" <ms...@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
>>>
>>>
>
>
Re: Failed to deploy artifacts: Could not transfer artifact xxxx
to/from apache.shapshots.https
Posted by Chris Lambertus <cm...@apache.org>.
Nexus is now back in service. Hopefully this will resolve the error 400s. If not, please let me know so we can troubleshoot further.
> On Oct 25, 2017, at 6:42 PM, Chris Lambertus <cm...@apache.org> wrote:
>
> Unfortunately, the restart seems to have killed nexus entirely. I will reach out to Sonatype for assistance.
>
>
>
>
>> On Oct 24, 2017, at 2:22 PM, Chris Lambertus <cm...@apache.org> wrote:
>>
>>
>>> On Oct 24, 2017, at 2:14 PM, Mike Drob <md...@apache.org> wrote:
>>>
>>> Everything meaning... all jenkins? local nexus hosts? how aggressive are we
>>> going here? :)
>>
>> Nexus.
>>
>> -Chris
>>
>>
>>
>>> On Tue, Oct 24, 2017 at 3:57 PM, Chris Lambertus <cm...@apache.org> wrote:
>>>
>>>>
>>>>> On Oct 24, 2017, at 1:26 PM, Marshall Schor <ms...@schor.com> wrote:
>>>>>
>>>>> The frequency of failure seems to have increased, at least for one of
>>>> our builds
>>>>> - it is now mostly failing (after uploading many of the artifacts to the
>>>> snapshot).
>>>>
>>>>
>>>>
>>>> I’ll start by restarting everything tonight around 0000 UTC. If that
>>>> doesn’t solve the issue, we’ll need Sonatype to look into it in more detail.
>>>>
>>>> -Chris
>>>> ASF Infra
>>>>
>>>>
>>
>
Re: Failed to deploy artifacts: Could not transfer artifact xxxx
to/from apache.shapshots.https
Posted by Chris Lambertus <cm...@apache.org>.
Unfortunately, the restart seems to have killed nexus entirely. I will reach out to Sonatype for assistance.
> On Oct 24, 2017, at 2:22 PM, Chris Lambertus <cm...@apache.org> wrote:
>
>
>> On Oct 24, 2017, at 2:14 PM, Mike Drob <md...@apache.org> wrote:
>>
>> Everything meaning... all jenkins? local nexus hosts? how aggressive are we
>> going here? :)
>
> Nexus.
>
> -Chris
>
>
>
>> On Tue, Oct 24, 2017 at 3:57 PM, Chris Lambertus <cm...@apache.org> wrote:
>>
>>>
>>>> On Oct 24, 2017, at 1:26 PM, Marshall Schor <ms...@schor.com> wrote:
>>>>
>>>> The frequency of failure seems to have increased, at least for one of
>>> our builds
>>>> - it is now mostly failing (after uploading many of the artifacts to the
>>> snapshot).
>>>
>>>
>>>
>>> I’ll start by restarting everything tonight around 0000 UTC. If that
>>> doesn’t solve the issue, we’ll need Sonatype to look into it in more detail.
>>>
>>> -Chris
>>> ASF Infra
>>>
>>>
>
Re: Failed to deploy artifacts: Could not transfer artifact xxxx
to/from apache.shapshots.https
Posted by Chris Lambertus <cm...@apache.org>.
> On Oct 24, 2017, at 2:14 PM, Mike Drob <md...@apache.org> wrote:
>
> Everything meaning... all jenkins? local nexus hosts? how aggressive are we
> going here? :)
Nexus.
-Chris
> On Tue, Oct 24, 2017 at 3:57 PM, Chris Lambertus <cm...@apache.org> wrote:
>
>>
>>> On Oct 24, 2017, at 1:26 PM, Marshall Schor <ms...@schor.com> wrote:
>>>
>>> The frequency of failure seems to have increased, at least for one of
>> our builds
>>> - it is now mostly failing (after uploading many of the artifacts to the
>> snapshot).
>>
>>
>>
>> I’ll start by restarting everything tonight around 0000 UTC. If that
>> doesn’t solve the issue, we’ll need Sonatype to look into it in more detail.
>>
>> -Chris
>> ASF Infra
>>
>>
Re: Failed to deploy artifacts: Could not transfer artifact xxxx
to/from apache.shapshots.https
Posted by Mike Drob <md...@apache.org>.
Everything meaning... all jenkins? local nexus hosts? how aggressive are we
going here? :)
On Tue, Oct 24, 2017 at 3:57 PM, Chris Lambertus <cm...@apache.org> wrote:
>
> > On Oct 24, 2017, at 1:26 PM, Marshall Schor <ms...@schor.com> wrote:
> >
> > The frequency of failure seems to have increased, at least for one of
> our builds
> > - it is now mostly failing (after uploading many of the artifacts to the
> snapshot).
>
>
>
> I’ll start by restarting everything tonight around 0000 UTC. If that
> doesn’t solve the issue, we’ll need Sonatype to look into it in more detail.
>
> -Chris
> ASF Infra
>
>
Re: Failed to deploy artifacts: Could not transfer artifact xxxx
to/from apache.shapshots.https
Posted by Chris Lambertus <cm...@apache.org>.
> On Oct 24, 2017, at 1:26 PM, Marshall Schor <ms...@schor.com> wrote:
>
> The frequency of failure seems to have increased, at least for one of our builds
> - it is now mostly failing (after uploading many of the artifacts to the snapshot).
I’ll start by restarting everything tonight around 0000 UTC. If that doesn’t solve the issue, we’ll need Sonatype to look into it in more detail.
-Chris
ASF Infra
Re: Failed to deploy artifacts: Could not transfer artifact xxxx
to/from apache.shapshots.https
Posted by Marshall Schor <ms...@schor.com>.
The frequency of failure seems to have increased, at least for one of our builds
- it is now mostly failing (after uploading many of the artifacts to the snapshot).
Filed a Jira https://issues.apache.org/jira/browse/INFRA-15366 . -Marshall
On 10/21/2017 10:04 AM, Martin wrote:
> 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" <ms...@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
>>>
>>>
>
>
Re: Failed to deploy artifacts: Could not transfer artifact xxxx to/from apache.shapshots.https
Posted by Martin <ma...@apache.org>.
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" <ms...@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
> >
> >
>
Re: Failed to deploy artifacts: Could not transfer artifact xxxx
to/from apache.shapshots.https
Posted by Gary Gregory <ga...@gmail.com>.
FYI: We seen the same errors for Log4j 2.
Gary
On Oct 12, 2017 07:26, "Marshall Schor" <ms...@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
>
>