[MRELEASE-880] Cannot restart from a failure

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.5
• Component/s: perform
• Assignee: Unassigned
• Reporter: Emmanuel Lécharny
• Created: 30/Jun/14 04:17
• Updated: 22/Dec/19 12:32
• Resolved: 22/Dec/19 12:32

Description

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 :

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.

(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.

Issue Links

• duplicates: SCM-695 Mvn release plugin problems with too many - in name
• is duplicated by: MRELEASE-876 Resume a release:perform in multimodule git project fails