MaaS, Correlation ID and scan counts implementation #718
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rated.matching.enabled is true
# Conflicts: # shared-version.properties # src/main/java/com/synopsys/integration/detect/configuration/DetectConfigurationFactory.java # src/main/java/com/synopsys/integration/detect/tool/signaturescanner/BlackDuckSignatureScannerOptions.java
… scan-type-specific codelocation counts for integrated matching
…ting counts to BD
…ses pure data classes
# Conflicts: # shared-version.properties
# Conflicts: # build.gradle # src/main/java/com/synopsys/integration/detect/configuration/DetectConfigurationFactory.java # src/main/java/com/synopsys/integration/detect/configuration/DetectPropertyFromVersion.java # src/main/java/com/synopsys/integration/detect/tool/signaturescanner/BlackDuckSignatureScannerOptions.java
# Conflicts: # build.gradle # src/main/java/com/synopsys/integration/detect/configuration/DetectConfigurationFactory.java # src/main/java/com/synopsys/integration/detect/lifecycle/run/DetectRun.java # src/main/java/com/synopsys/integration/detect/lifecycle/run/step/IntelligentModeStepRunner.java # src/main/java/com/synopsys/integration/detect/lifecycle/run/step/SignatureScanStepRunner.java # src/main/java/com/synopsys/integration/detect/tool/signaturescanner/BlackDuckSignatureScannerOptions.java
# Conflicts: # src/main/java/com/synopsys/integration/detect/lifecycle/run/step/IntelligentModeStepRunner.java
# Conflicts: # src/main/java/com/synopsys/integration/detect/lifecycle/run/DetectRun.java
# Conflicts: # src/main/java/com/synopsys/integration/detect/Application.java # src/main/java/com/synopsys/integration/detect/lifecycle/run/DetectRun.java # src/main/java/com/synopsys/integration/detect/lifecycle/run/step/RapidModeStepRunner.java # src/main/java/com/synopsys/integration/detect/lifecycle/run/step/SignatureScanStepRunner.java
# Conflicts: # src/main/java/com/synopsys/integration/detect/configuration/DetectConfigurationFactory.java # src/main/java/com/synopsys/integration/detect/lifecycle/run/DetectRun.java # src/main/java/com/synopsys/integration/detect/lifecycle/run/step/IntelligentModeStepRunner.java # src/main/java/com/synopsys/integration/detect/tool/signaturescanner/BlackDuckSignatureScannerOptions.java
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Changes to support correlated scanning.
Github Issues
Provided unique Correlation ID to SIG Scanner - IDETECT-1875
Correlation ID is written to BDIO Header - IDETECT-2871
When MaaS is enabled, scan count is submitted to new Black Duck API - IDETECT-3095
New optional Detect property to enable MaaS and Correlation ID mode - DETECT-3448
Scan counts are calculated - IDETECT-3505