Timing Issue in build running

Hi. We haven’t purchased the product yet, we’re in a pilot. In the pilot, we encountered a timing issue. The scans took a long time even though we expected to scan only changed files. The scan took between 30% to 100% compared to running the build without the scan. Is this how it’s supposed to work? It’s problematic.
Thank you

Hi,

Welcome to the community!

There’s very little to go on here. Can you add -Dsonar.verbose=true to your analysis command line and provide the full analysis log, redacted as necessary?

The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.

This guide will help you find them.

 
Thx,
Ann