fix: temp fix for suppressed bdba (and impact analysis) errors
@@ -15,6 +15,7 @@ import java.util.Set;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
+import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import com.google.gson.Gson;
@@ -155,6 +156,7 @@ import com.synopsys.integration.util.NameVersion;
import com.synopsys.integration.util.OperatingSystemType;
public class OperationFactory { //TODO: OperationRunner
+ private final Logger logger = LoggerFactory.getLogger(this.getClass());
private final DetectDetectableFactory detectDetectableFactory;
private final DetectFontLoaderFactory detectFontLoaderFactory; //TODO: Eh? Only need it if you want to do risk reports.
@@ -584,11 +586,15 @@ public class OperationFactory { //TODO: OperationRunner
}
public void publishBinaryFailure(String message) {
+ // TODO how should the arg be used? Ignoring it is hiding important error info; adding this for now:
+ logger.error("Binary scan failure: {}", message);
statusEventPublisher.publishStatusSummary(Status.forTool(DetectTool.BINARY_SCAN, StatusType.FAILURE));
exitCodePublisher.publishExitCode(ExitCodeType.FAILURE_BLACKDUCK_FEATURE_ERROR, "BINARY_SCAN");
}
public void publishImpactFailure(Exception e) {
+ // TODO how should the arg used? I'm guessing ignoring it might hide important error info here too; adding this for now:
+ logger.error("Impact analysis failure: {}", e.getMessage());
statusEventPublisher.publishStatusSummary(Status.forTool(DetectTool.IMPACT_ANALYSIS, StatusType.FAILURE));
exitCodePublisher.publishExitCode(ExitCodeType.FAILURE_BLACKDUCK_FEATURE_ERROR, "IMPACT_ANALYSIS");
}
