The last successful analysis on this project was 24th Jan 2024.
I’ve read various other similar reports that have been raised since 1st Feb - which suggested deleting the Sonar project & re-importing from GitHub. So I did this. The first auto-analysis on the new project failed (with the above Analysis ID).
Just posting here to say that this issue is still impacting our project.
Is there really no way of retrieving analysis logs ourselves?
Hello @marktarry-mobysoft ,
Apologies for the delay to get back to you,
The logs seem to indicate that the cause of your issue is similar than the one of this thread.
@ilia hinted a workaround in this post and there is a fix planned to be released beginning of April. Could you please check that you are impacted as well by trying to suggested workaround?
Is there really no way of retrieving analysis logs ourselves?
As of today, some specific failures (timeout, missing sources) will bubble up to the user interface, but not all of them. There is room for improvements about this, and we currently have in our backlog to improve the user experience during failures of autoscan to give more power to the users.
Hope my answer helps
Thanks @benjamin.raymond
Given the time that has elapsed, since we first saw the issue, we’ve had to bypass sonar analysis on this codebase for the time being. Not ideal, but the team had other work which was blocked.
I’ve passed on your comments to the team.
There is room for improvements about this, and we currently have in our backlog to improve the user experience during failures of autoscan to give more power to the users.
Agreed. The reliance on posting autoscan failures to this forum, and the subsequent potential for delays, is a significant detractor when deciding whether to use autoscan. I look forward to hearing what the Sonar team comes up with to tackle the issue.
In the meantime, I’m closing this thread.
Thanks again
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.