Skip to content

Conversation

@nichollsdave
Copy link
Collaborator

This was at the request of a customer. Previously this would wait for the first matching code location and ignore the others. When using package manager scan as well as signature scan you will get at least 2 code locations. If you then also snippet scan one of these code locations (* scan) will have 2 scans, one FS and one SNIPPET.

Modified the wait code to wait for all matching code locations. This involved also modifying the code that determines if there should be a snippet scan to wait for too, as BDIO scans will not have a second SNIPPET scan.

Tested thoroughly and the only scenario it does not handle is if there are previous code location names that also match e.g. '<code_location_name> bdio 21' when this current scan only includes 20 bdio scans. In this scenario it will wait and timeout for 21 to have a 'newer' scan. The flip side of this is if we ignore code locations without newer scans then perhaps we say it is finished when it hasn't been created yet. Food for thought.

…performing BOM scans esepcially without aggregating. Will wait for all code locations to complete, modified snippet scan wait criteria to only apply to relevant code locations
Copy link
Contributor

@gsnyder2007 gsnyder2007 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks for the contribution.

@gsnyder2007 gsnyder2007 merged commit 7c3aadd into blackducksoftware:master Nov 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants