Are you running fortify scan through sourceanalyzer for MSBuild? Are you running it with Jenkins? Jenkins node is running with Windows? May be following a process describe here.
Following steps working fine if you are running with powershell or cmd, but not working when you run with Jenkins? Scan is failing on scan step?
[error]: Unable to load build session with ID " fortify_sample". See log file for more details.
Provable solution:
Please check the output of the MSBuild step. There will be some .txt file generated for the build step. Please check the location of the files generated. If the files are not generated, that means there are some permission issue of the user under which Jenkins service or agent service is running.
In my case the issue was my Jenkins service was running under local system and it was trying to write to C:\Windows\system32\config\systemprofile\AppData.
I changed service running user id to a service account and started working fine.
Following steps working fine if you are running with powershell or cmd, but not working when you run with Jenkins? Scan is failing on scan step?
sourceanalyzer -b fortify_sample -clean sourceanalyzer -b fortify_sample msbuild Fortify.Samples.sln /t:ReBuild sourceanalyzer -b fortify_sample -scan -f result.fprSaying-
[error]: Unable to load build session with ID " fortify_sample". See log file for more details.
Provable solution:
Please check the output of the MSBuild step. There will be some .txt file generated for the build step. Please check the location of the files generated. If the files are not generated, that means there are some permission issue of the user under which Jenkins service or agent service is running.
In my case the issue was my Jenkins service was running under local system and it was trying to write to C:\Windows\system32\config\systemprofile\AppData.
I changed service running user id to a service account and started working fine.
No comments:
Post a Comment