maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Green (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MRELEASE-880) Cannot restart from a failure
Date Tue, 07 Apr 2015 14:21:12 GMT

    [ https://issues.apache.org/jira/browse/MRELEASE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483229#comment-14483229
] 

James Green commented on MRELEASE-880:
--------------------------------------

In our case (see the markmail link) SNAPSHOTs work fine but exhibit no HTTP Authentication.
RELEASEs see a 401 followed by 200 per artefact, and eventually it ends (at a random point)
with a 401 and a SocketException (broken pipe) on write (-X during the build is helpful here).

We have haproxy 1.5.11 in between Jenkins and Nexus, and I am not aware of anything special
in terms of packaging. The project itself consists of thirty-four artefacts. By the looks
of things it can fail pretty close to the start.

What I have not determined is which component is to blame. And I do not have much other than
the switching on of logging by suggestion to investigate further with.

We are using Maven 3.0.4 (Ubuntu package).

> Cannot restart from a failure
> -----------------------------
>
>                 Key: MRELEASE-880
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-880
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: perform
>    Affects Versions: 2.5
>            Reporter: Emmanuel Lecharny
>            Priority: Blocker
>
> It's currently quite impossible to cut a release on a big Apache project if the remote
server has hickups. 
> I tried to release Apache Directory Server this morning, and for some unknown reasons,
I get various and random failures like :
> {noformat}
> Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy
> (default-deploy) on project apacheds-core-api: Failed to deploy
> artifacts: Could not transfer artifact
> org.apache.directory.server:apacheds-core-api:jar:tests:2.0.0-M17
> from/to apache.releases.https
> (https://repository.apache.org/service/local/staging/deploy/maven2):
> Failed to transfer file:
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/directory/server/apacheds-core-api/2.0.0-M17/apacheds-core-api-2.0.0-M17-tests.jar.
> Return code is: 400, ReasonPhrase: Bad Request.
> {noformat}
> (note that if I restart the {{release:perform}}, the error I will get will be different).
> There is no way I can restart the perform from another point (like the failing module)
but the very beginning.
> At the very end, I did a {{mvn deploy -Papache-release}} from {{target/checkout}} as
a workaround...
> The real pb is that the release plugin should not simply bail when it gets some error
attempting to reach a remote server. Asking the user about doing a retry should be the way
to go.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message