Other Considerations About the Project-Branching Operation

The following are additional notes about the branching operation:

•

Users can run parallel branching operations on the same source project.

•

If a user initiates the branching process in one browser tab, opens the same Code Insight instance in another browser tab, and then navigates to the branched project in the second tab, the branching status information for the branched project should be the same as in the first browser tab.

•

The project-branching session might time out (for example, due to a delayed scan phase because the scan is queued). Should the session time out, the user must use the DELETE projects/{projectId} REST API to remove the branched project from Code Insight. Once the project is deleted, the user can then rerun the Branch Project wizard to recreate the branched project and initiate the branching operation.

•

Should an SCM synchronization or the scan fail during the automated part of the branching operation, the branch process is terminated. The user can navigate to the Summary tab of the branched project to view any captured scan details.

•

During the branching process, the branch codebase is scanned before the import phase begins. Therefore, any file association for a source inventory item most likely also exists in the branch inventory item by the time the import starts. By design, when the import detects the same file association for both the source and branch inventory item, it adds no new file association to the branch inventory item. However, when the import processes this association, a “duplicate entry” exception similar to the following might be logged:

Duplicate entry ‘entry_id’ for key 'pse_inventory_group_files.UNIQ_FILE_GROUP

This exception is benign and has no impact on the regular file-processing behavior—that is, the existing file association is retained; no new file association is added.