What is the criteria used for creating multiple tasks when importing ClearCase source code while using the synchronizer?
I would like to understand the rational behind the number of tasks created when performing a single import using the ClearCase Synchronizer. In the example below, the single import created 66 separate work items (i.e. tasks) over the course of ~38 hours in order to complete.
What determines the number of tasks created? Why can't it just be one task for the whole import?
A sample of 6 tasks created by the synchronizer are listed below:
The change sets above were all created and added by our synchronizer account.
Any input would be appreciated.
Thanks
|
Accepted answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 09 '16, 2:28 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The synchronizer currently creates a separate task for each change set.
As I recall, the rationale for creating a separate task for each change set is that a description of the imported activities is stored in the Description of the task, and if only one task were created for a given import, the information could overflow maximum field length of the Description field. Stephane Couillaud selected this answer as the correct answer
Comments I had a couple follow up questions:
1) It would appear that the state of each task remains as "New" following an import or a synchronization with the ClearCase synchronizer. Is that the expected behavior? Or should these be closed automatically by the importer/synchronizer once the import/sync is completed?
2.) Where does each task inherit the value set for "Filed Against"?
1
Geoffrey Clemm
commented Sep 21 '16, 11:19 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
(1) Yes, that is the expected behavior.
|