It's all about the answers!

Ask a question

Unable to Deliver new documents due to conflict


Matthew Widdup (11) | asked Jun 01 '10, 9:59 p.m.
Hi,

I'm currently experiencing an intermittent problem (maybe 40% occurrence) where I am unable to deliver a change set due to a conflict.

The files I'm attempting to deliver are new (nothing to conflict with) and are already checked-in. So the suggested solution is not possible as far as I'm aware.

I am yet to see any reason why sometimes delivery works and sometimes it fails.

Any help would be great.

Error:

Problem

An error occurred during "Deliver".

Cannot deliver changes since they would create conflicts for [UUID _czCu4F5MEd-9wrftVGTFBQ]. Try accepting all incoming changes, resolve the conflicts, then deliver again.

2 answers



permanent link
Geoffrey Clemm (30.1k33035) | answered Jun 02 '10, 12:45 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
It is likely you are seeing defect 14691. This is currently targeted
for milestone M7 of 3.0. Until that is fixed, there are workarounds
described in that work item for this problem.

Cheers,
Geoff

On 6/1/2010 10:07 PM, MattWiddup wrote:
Hi,

I'm currently experiencing an intermittent problem (maybe 40%
occurrence) where I am unable to deliver a change set due to a
conflict.

The files I'm attempting to deliver are new (nothing to conflict with)
and are already checked-in. So the suggested solution is not possible
as far as I'm aware.

I am yet to see any reason why sometimes delivery works and sometimes
it fails.

Any help would be great.

Error:

Problem
An error occurred during "Deliver".

Cannot deliver changes since they would create conflicts for . Try accepting all incoming changes,
resolve the conflicts, then deliver again.


permanent link
Michael Wallach (6) | answered Feb 08 '11, 6:38 p.m.
How do I see the workaround for 14691? I've looked around the site but can't seem to be able to find where the defects and their workarounds are listed.

Thx, Mike

It is likely you are seeing defect 14691. This is currently targeted
for milestone M7 of 3.0. Until that is fixed, there are workarounds
described in that work item for this problem.

Cheers,
Geoff

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.