Project Management
The following enhancement is now available for managing projects.
Project Deletions Now Queued and Run in Background
Previously project deletions were performed as soon as the Delete Project option in the UI was selected or the Delete Project API was issued. However, the deletion of large projects along with other events across Code Insight could cause issues such as project deadlocks or system timeouts.
Starting in this release, project deletions now added to the new Code Insight Jobs Queue and run in the background. When project deletions are triggered concurrently, they are scheduled in the queue and run one at a time to help avoid contention with other projects and events. Users can monitor the deletion progress in the Jobs queue.
See also REST API Enhancements in this document for the API changes that support this enhancement to the project deletion process.
For complete details about queued project deletions and about the new Jobs queue in the UI, see the “Deleting a Project” and “Code Insight Jobs Queue” sections, respectively, in the Code Insight User Guide.
Report Generation Not Allowed During a Scan on Same Project (and Vice Versa)
To help prevent deadlocks on a project, Code Insight has implemented the following behavior to block users from triggering a scan and a report in parallel on the same project:
| • | If a user attempts to generate any report (standard or custom) for a project for which a scan or rescan is in queue or in progress, the Generate Selected Report button on the Reports tab for the project is disabled. Once the scan completes, button is re-enabled. |
| • | If a user attempts to trigger a scan or rescan on a project while a report is in queue or in progress for the same project, a pop-up message is displayed, explaining that a report is in progress and that the user must wait until the operation is complete before attempting to trigger the scan. |
When a user calls the REST API to attempt either of the above actions, the response explains the error. See Updates to Existing APIs.
In all cases, you can attempt the scan or report generation again once the parallel event is finished.