ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Klaas Prause (JIRA)" <>
Subject [jira] Commented: (IVY-1073) publish should be an atomic operation
Date Wed, 29 Apr 2009 14:53:32 GMT


Klaas Prause commented on IVY-1073:

maybe ivy could establish some locking mechanism via lock files or rename the directory after
the publish is finished and delete it if publishing fails.

> publish should be an atomic operation
> -------------------------------------
>                 Key: IVY-1073
>                 URL:
>             Project: Ivy
>          Issue Type: Improvement
>    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.

View raw message