-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 1.596.3
BlackDuck Hub Plugin 2.2.1
BlackDuck Hub 4.2.0
Windows 2012 R2
Cancelling a running scan does not terminate the scan-cli process started by the plugin. This results in the scan-cli leaving files open, which can interfere with new builds.
Log of the cancelled job:
INFO: Total time: 5033 seconds to scan path: C:\jenkins-slave\workspace\pa-trunk INFO: Post Scan... java.lang.InterruptedException java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:146) at hudson.remoting.Channel.call(Channel.java:751) at com.blackducksoftware.integration.hub.jenkins.scan.BDCommonScanStep.runScan(BDCommonScanStep.java:270) at com.blackducksoftware.integration.hub.jenkins.PostBuildHubScan.perform(PostBuildHubScan.java:194) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1783) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Finished running Black Duck Scans. Build step 'Black Duck Hub Integration' changed build result to UNSTABLE
Process is still running:
