Copying a Project
The Project Copy feature copies the information from an existing Code Insight project—including its project settings, user information, source-code files and folders, scan evidence, inventory details, alerts, and certain scan history details—to a new project. Project Copy offers an alternative to project-branching and has the following advantages over the branching process:
|
•
|
No scan needed—The branching process triggers a full scan of the branched project (which, in most cases, is not needed because the source project already contains base-line scan results that are copied to the branched project). In contrast, the Project Copy process simply copies all scan results from the source project to the target project without running a scan on the target. |
|
•
|
Previously removed false-positive inventory not reinstated—The scan on a branched project can pull in false-positive inventory that might have been cleaned up in the source project. On the other hand, the Project Copy process copies inventory information “as is” from the source project to the target project. If information in the source project had been cleaned up, it remains cleaned up in the target because no scan is triggered on the copied data. |
|
•
|
No need to confirm project settings prior to the copy—As part of the branch-project process, you must confirm individual project settings for the branched project before running the branch process. (In most cases, no changes are needed.) During the Project Copy, source project settings are simply copied to the target project without the extra step to confirm settings. If any changes are needed, you can apply them to the target project after the copy. |
The following sections describe how you initiate a Project Copy and what happens during the copy process: