An active connection syncs vulnerability data from Black Duck SCA to Polaris at least once a day. You can also manually sync data at the organization or project level.
Vulnerabilities are synced from Black Duck SCA to Polaris once every 24 hours. You can also manually trigger a sync, either at the organization level or for individual projects.
When a sync is triggered, Polaris retrieves a list of modified projects and versions from Black Duck SCA via the connection. External Analysis tests are then started for every mapped Polaris branch that has data available to import.
Sync Black Duck SCA data for your organization
From the page:
In the Black Duck SCA section, identify the connection to sync, then select Sync now from the three-dot menu.
The Last Synced column is updated when the sync task is complete. A completed sync means that Black Duck SCA data has been mapped to Polaris, and new external analysis tests have been submitted to the test scheduler to run.
Sync Black Duck SCA data for a project
For projects already mapped to Black Duck SCA from previous syncs, you can trigger a sync from the Project Settings page.
Data is synced to all the branches in the project.