Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <1311906365.1241078495673.JavaMail.jira@brutus>
Date: Thu, 30 Apr 2009 01:01:35 -0700 (PDT)
From: "Maarten Coene (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Commented: (IVY-1073) publish should be an atomic operation
In-Reply-To: <317013059.1241016810337.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/IVY-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704520#action_12704520 ] 

Maarten Coene commented on IVY-1073:
------------------------------------

What resolver do you use for publishing? The filesystem resolver has atomic publish support:
http://ant.apache.org/ivy/history/2.1.0-rc1/resolver/filesystem.html

> publish should be an atomic operation
> -------------------------------------
>
>                 Key: IVY-1073
>                 URL: https://issues.apache.org/jira/browse/IVY-1073
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 1.4.1, 2.1.0-RC1
>            Reporter: Klaas Prause
>
> The publish action is not atomic, so it does not succeed as one action or fails completly. This has two problems:
> 1. We are using ivy not only for publishing JARs but also for the releaseables including EARs and WARs. So the publish target sometimes uploads more than 50MB what takes a few seconds. Our continious integration server builds with ~6 build queues. So it often happens that a build is checking for new versions and finds a version that is currently in the process of publishing. The retrieve fails because not all items are uploaded and the build fails.
> 2. If a build did not produce all needed artifacts (a clear build error) Ivy publish does not tests for missing artifacts prior starting the upload. If an artifact is missing the publish fails but the already uploaded files are not deleted. All builds other builds try to retrieve the incomplete published artifact and fail.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.