We have a repo that shows that all is ok but if you look into the action log details the build is failed. According to Github we need to contact Sonarcloud for this. Since this is private info I cannot share it publicly. Any suggestion how we can resolve this?
Hey there.
This is a community forum, so we invite you redact the logs as necessary. At a minimum, we need to know what the failure actually is. Screenshots of GitHub showing the build as successfully but the log showing a failure would also be helpful!
Sharing code or logs
When possible, we prefer that users share code/logs publicly, redacted as necessary, so that all users can benefit from these interactions in the Community. Our default is transparency.
Hi Colin,
We do not want to share our code or log publicly. How can we get support from you? Hope to hear soon form you.
Regards,
Reinier
Hey @reiniertvb
This is a community forum. The alternative is to inquire about Sonar Commercial Support.
So we would request you redact information as neccessary, or at a minimum share an error log.
The build shows that it is succesfull:
But the log shows:
I hope this helps. If not I suggest we find a different way to assist us.
Suggestion: Have a call so I can share the needed info. Or let us mail it to you.
Again, this is a Community forum. I’m sorry, but without additional details (logs, pipeline configuration) it won’t be possible to help you in this setting.
Remark of Github:
I’m not seeing anything in the workflow file content that would affect the status being set for the step. Looking again at the job log, I initially suspect this is related to the use of SonarScanner alongside your dotnet build.
After the build failure from the dotnet build command, we see dotnet-sonarscanner end still runs and completes.
Something related to SonarScanner could be either intentionally or unintentionally catching / preventing dotnet build 's non-zero exit code being raised. If that’s happening, Actions doesn’t interpret a failure for the step since it didn’t receive a non-zero exit code.
If possible, you can consider testing this by commenting out the SonarScanner lines from the step and seeing if the build failure is raised as expected in a separate workflow run with the changes made.