[BUG] scan command not working when used in jenkins script

[Yogesh-Tiwari]

Description:

• When running the command sf scanner run -t "./**/*.cls" for the jenkins job's workspace folder for a PR raised gives error:
  "The specified target wasn't processed by any engines. Use the --engine parameter to select a different engine or specify a different target. Specified target: ./**/*.cls" and no files are scanned even if the .cls files are present in the job's workspace.
• The same command when run in the actual sfdx project folder it works fine and the classes scan result is shown in console.

Details:

• Operating System. Example: Windows 11
• sf scanner plugin version: 3.24.0
• Salesforce CLI version: @salesforce/cli/2.38.7

[stephen-carter-at-sf]

Did you instead mean to do
sf scanner run -t "./**/*.cls"
?

[Yogesh-Tiwari]

Hi @stephen-carter-at-sf yes I am trying to run the same command.

[stephen-carter-at-sf]

@Yogesh-Tiwari
Oh I see the markdown in github is removing what you typed visually. Are you calling this from a jenkinsFile or something? If so, can you show me the code where you actually make this call.

Also, can you confirm that the environment that you are running this from in jenkins has your files actually checked out. Doing an ls or something first may help you confirm it in the logs.