kspoojary (Community Member) asked a question.

Pipeline scan failing with timeout error.

Hi , I had setup a pipeline scan in azure devops couple of weeks ago. andIt was working fine. But form last few days it started failing with timeout error. Pipeline scan was taking 12 minutes earlier but now it is taking more time and because of 60 minutes time out limit it is falling. I check the status of the scan and it is "Started".

 

One thing I observed in the response of https://api.veracode.com/pipeline_scan/v1/scans/ee1624de-8fad-4938-9302-cf99a6d963fe/findings API is that third party modules also selected.

 

API response for reference

{

  "_links": {

    "root": {

      "href": "/"

    },

    "self": {

      "href": "/scans/ee1624de-8fad-4938-9302-cf99a6d963fe/findings"

    },

    "help": {

      "href": "https://help.veracode.com/reader/tS9CaFwL4_lbIEWWomsJoA/ovfZGgu96UINQxIuTqRDwg"

    }

  },

  "scan_id": "ee1624de-8fad-4938-9302-cf99a6d963fe",

  "scan_status": "STARTED",

  "message": "",

  "modules": [

    "bin/ContentManagement.dll",

    "bin/runtimes/linux-musl-x64/native/Magick.Native-Q16-x64.dll.so",

    "bin/runtimes/linux-x64/native/Magick.Native-Q16-x64.dll.so"

  ],

  "modules_count": 3,

  "findings": []

}

 

 

In the modules slected I am expecting only ContentManagement.dll but Magick.Native-Q16-x64.dll.so is also getting selected and because of this my pipeline scan is timing out.

 

Temporarily I removed that third party dll from my solution and ran the new pipeline scan with this build and it worked.

 

Is there way to specify the module selection in pipeline scan?

 

 


Topics (4)

No articles found
Loading

Ask the Community

Get answers, share a use case, discuss your favorite features, or get input from the community.