Sync Job failing
How can I tell why this job is failing? It was working before and I can't recall changing anything that would cause it to fail.
Sync:
action: SYNCHRONIZE
synchronization stream location string: Stream|URI:itemOid/com.ibm.team.scm.Workspace/_8sNx0LMLEd2DMLmR6ZEj-g
synchronizer version number 'I20081024-1335'
running on host 'durango'
Creating baseline in component: foobar
Creating baseline in component: kungfoo
Computing changes in component: foobar
Computing changes in component: kungfoo
Updating file: kungfoo/lwp/AntTest/typeTest/hw.jsp
Checking in brought over changes
WARNING: Could not create task named: Synchronize Task
WARNING: Could not update comment on task: (JzLocation: BaselineControlledFolder||Component|name:SYNC||Workspace|URI:itemOid/com.ibm.team.scm.Workspace/_EJ7OwLZoEd24gq__DzjOUw)
WARNING: Could not update task list for: (JzLocation: ChangeSet|URI:itemOid/com.ibm.team.scm.ChangeSet/_5zOAs7o4Ed24gq__DzjOUw)
WARNING: Could not create task named: Synchronize Task
Synchronization exception: Repository resource does not exist: BaselineControlledFolder||Component|name:SYNC||Workspace|URI:itemOid/com.ibm.team.scm.Workspace/_EJ7OwLZoEd24gq__DzjOUw
Sync:
action: SYNCHRONIZE
synchronization stream location string: Stream|URI:itemOid/com.ibm.team.scm.Workspace/_8sNx0LMLEd2DMLmR6ZEj-g
synchronizer version number 'I20081024-1335'
running on host 'durango'
Creating baseline in component: foobar
Creating baseline in component: kungfoo
Computing changes in component: foobar
Computing changes in component: kungfoo
Updating file: kungfoo/lwp/AntTest/typeTest/hw.jsp
Checking in brought over changes
WARNING: Could not create task named: Synchronize Task
WARNING: Could not update comment on task: (JzLocation: BaselineControlledFolder||Component|name:SYNC||Workspace|URI:itemOid/com.ibm.team.scm.Workspace/_EJ7OwLZoEd24gq__DzjOUw)
WARNING: Could not update task list for: (JzLocation: ChangeSet|URI:itemOid/com.ibm.team.scm.ChangeSet/_5zOAs7o4Ed24gq__DzjOUw)
WARNING: Could not create task named: Synchronize Task
Synchronization exception: Repository resource does not exist: BaselineControlledFolder||Component|name:SYNC||Workspace|URI:itemOid/com.ibm.team.scm.Workspace/_EJ7OwLZoEd24gq__DzjOUw
3 answers
The Work Item Categories for the Project Area was associated with an archived Team Area. I recall archiving a Team Area last week but didn't understand the consequences (the initial association was implicit).
To fix it, I disassociated and re-associated the new team. The reason it appeared to work earlier today was because it didn't have anything to sync, so it didn't need to create a work item.
I was also mistaken to think the "IGNORE_TASK_CREATION_FAILURE" properties (both providers) would prevent the sync job from trying to create a work item.
To fix it, I disassociated and re-associated the new team. The reason it appeared to work earlier today was because it didn't have anything to sync, so it didn't need to create a work item.
I was also mistaken to think the "IGNORE_TASK_CREATION_FAILURE" properties (both providers) would prevent the sync job from trying to create a work item.
Erik:
Just to confirm, once you associated the category to a new team, the
sync succeeded? In particular, did the synchronization error about:
Synchronization exception: Repository resource does not
exist:
BaselineControlledFolder||Component|name:SYNC||Workspace|URI:itemOid/com.ibm.team.scm.Workspace/_EJ7OwLZoEd24gq__DzjOUw
go away?
If so, that's good, but I'll still file a workitem asking that the
error/warning messages be improved, and to figure out why the failure to
create the task (which is just a warning) resulted in a synchronization
exception.
Cheers,
Geoff
eanderso wrote:
Just to confirm, once you associated the category to a new team, the
sync succeeded? In particular, did the synchronization error about:
Synchronization exception: Repository resource does not
exist:
BaselineControlledFolder||Component|name:SYNC||Workspace|URI:itemOid/com.ibm.team.scm.Workspace/_EJ7OwLZoEd24gq__DzjOUw
go away?
If so, that's good, but I'll still file a workitem asking that the
error/warning messages be improved, and to figure out why the failure to
create the task (which is just a warning) resulted in a synchronization
exception.
Cheers,
Geoff
eanderso wrote:
The Work Item Categories for the Project Area was associated with an
archived Team Area. I recall archiving a Team Area last week but
didn't understand the consequences (the initial association was
implicit).
To fix it, I disassociated and re-associated the new team. The reason
it appeared to work earlier today was because it didn't have anything
to sync, so it didn't need to create a work item.
I was also mistaken to think the
"IGNORE_TASK_CREATION_FAILURE" properties (both providers)
would prevent the sync job from trying to create a work item.
Yes, I got a successful run after changing to the new team:
Sync:
action: SYNCHRONIZE
synchronization stream location string: Stream|URI:itemOid/com.ibm.team.scm.Workspace/_8sNx0LMLEd2DMLmR6ZEj-g
synchronizer version number 'I20081024-1335'
running on host 'durango'
Creating baseline in component: foobar
Creating baseline in component: kungfoo
Computing changes in component: foobar
Computing changes in component: kungfoo
Updating file: kungfoo/lwp/AntTest/typeTest/hw.jsp
INFO: Duplicate content write to Jazz ignored, no new state created.
Checking in brought over changes
Computing changes in synchronized stream
Synchronization completed without conflicts
all:
BUILD SUCCESSFUL
Total time: 33 seconds
Sync:
action: SYNCHRONIZE
synchronization stream location string: Stream|URI:itemOid/com.ibm.team.scm.Workspace/_8sNx0LMLEd2DMLmR6ZEj-g
synchronizer version number 'I20081024-1335'
running on host 'durango'
Creating baseline in component: foobar
Creating baseline in component: kungfoo
Computing changes in component: foobar
Computing changes in component: kungfoo
Updating file: kungfoo/lwp/AntTest/typeTest/hw.jsp
INFO: Duplicate content write to Jazz ignored, no new state created.
Checking in brought over changes
Computing changes in synchronized stream
Synchronization completed without conflicts
all:
BUILD SUCCESSFUL
Total time: 33 seconds