ClearCase Synchronization Error
When running a synchronization job in the ClearCase Synchronization Engine, I get the following error message (unfortunately in German language; see my other posting :cry:
The meaning is deliver did not run, because the associated Work Item has no Iteration planned.
But which Work Item? The Work Item Template set in the definition of the synchronized stream has one set and even if I remove the template and have Work Item, this error occures.
javax.wvcm.WvcmException: 'bergeben' ist fehlgeschlagen. Die Vorbedingungen wurden nicht erfllt: Das zugeordnete Arbeitselement muss angeben, fr welche Iteration die Arbeit geplant ist.
The meaning is deliver did not run, because the associated Work Item has no Iteration planned.
But which Work Item? The Work Item Template set in the definition of the synchronized stream has one set and even if I remove the template and have Work Item, this error occures.
Accepted answer
In the Eclipse client, open the workspace named CLONE_xxx (where "xxx"
is the name of your synchronized stream). You can use "Search -> Jazz
Source Control -> Repository/Workspaces/Streams" to find it.
Then in the workpace editor, right click over the imported component,
and select "Show -> History". This will give you the list of
change-sets and their associated work items. Open the last couple of
work items, and you should find the one that does not have its
PlannedFor attribute set. Set it to be the current iteration, and retry
the sync.
Cheers,
Geoff
On 3/14/2012 2:12 PM, hajo62 wrote:
is the name of your synchronized stream). You can use "Search -> Jazz
Source Control -> Repository/Workspaces/Streams" to find it.
Then in the workpace editor, right click over the imported component,
and select "Show -> History". This will give you the list of
change-sets and their associated work items. Open the last couple of
work items, and you should find the one that does not have its
PlannedFor attribute set. Set it to be the current iteration, and retry
the sync.
Cheers,
Geoff
On 3/14/2012 2:12 PM, hajo62 wrote:
'bergeben' ist
fehlgeschlagen. Die Vorbedingungen wurden nicht erfllt: Das
zugeordnete Arbeitselement muss angeben, fr welche Iteration die
Arbeit geplant ist.
2 other answers
One thing to keep in mind is that a "synchronize" is not just a "build"
(even though it uses the build machinery in its implementation). But
there is an analogy that might help explain the behavior. Suppose that
as part of your build, you checked in some new changes, and then you
want the build to deliver those changes to some stream (in the
Synchronize case, the "new changes" are changes coming over from
ClearCase, and the "stream" is the synchronized stream). But now
suppose the stream you are delivering to has constraints, such as "there
must be a work item associated with any change set, and that work item
must be planned for the current release". The attempt by the "build" to
deliver the change set to the stream will fail unless that condition is
met (or unless that condition is removed from the stream).
That is what happened in your case. The project area containing the
synchronized stream had this constraint. So you either had to use a
work item template in the synchronized stream that satisfied this
constraint, or you had to remove the constraint (or change the owner of
the synchronized stream to be a project area without this constraint).
Also note that although changing the work item template will fix
subsequent sync requests, it will not "fix" the synchronize that failed
(it sounds like this is what you tried), because a new work item is
created (by copying the "template" work item) for each sync, so updating
the work item template does not update the work item actually associated
with the previous sync attempt.
Cheers,
Geoff
On 3/15/2012 4:57 AM, hajo62 wrote:
(even though it uses the build machinery in its implementation). But
there is an analogy that might help explain the behavior. Suppose that
as part of your build, you checked in some new changes, and then you
want the build to deliver those changes to some stream (in the
Synchronize case, the "new changes" are changes coming over from
ClearCase, and the "stream" is the synchronized stream). But now
suppose the stream you are delivering to has constraints, such as "there
must be a work item associated with any change set, and that work item
must be planned for the current release". The attempt by the "build" to
deliver the change set to the stream will fail unless that condition is
met (or unless that condition is removed from the stream).
That is what happened in your case. The project area containing the
synchronized stream had this constraint. So you either had to use a
work item template in the synchronized stream that satisfied this
constraint, or you had to remove the constraint (or change the owner of
the synchronized stream to be a project area without this constraint).
Also note that although changing the work item template will fix
subsequent sync requests, it will not "fix" the synchronize that failed
(it sounds like this is what you tried), because a new work item is
created (by copying the "template" work item) for each sync, so updating
the work item template does not update the work item actually associated
with the previous sync attempt.
Cheers,
Geoff
On 3/15/2012 4:57 AM, hajo62 wrote:
Thanks Geoff, that solved my problem.
From my point of view, it's not so easy to understand, that a Work
Item connected to an old Build inhibits
new builds to execute. If I saw correct, the synchronization
(connected to that Work Item) did occure, so that data later
synchronized would fit.