We are facing a Quality Gate failure with the following error message:
Quality Gate failed: Could not fetch quality gate status: b’{“errors”:[{“msg”:“Analysis with id \”
We have already tried the following troubleshooting steps without success:
Reviewing Logs: We checked the SonarQube logs for any additional error messages or warnings, but the provided error message is the only information we have at the moment.
Analyzing Analysis: We examined the analysis being performed on the codebase to see if there were any issues with the project configuration or parameters. Everything appeared to be in order.
Checking Server Resources: We verified that the SonarQube server has sufficient resources (CPU, memory, disk space) to handle the analysis.
we have not been able to identify the root cause of this issue. As a result, we are reaching out to the Sonar community for assistance
If anyone has encountered a similar problem or has suggestions on how to resolve this Quality Gate issue, please share your experiences and insights with us. Your expertise could be invaluable in helping us resolve this problem and ensure the continued effectiveness of our code quality analysis.
What do you mean by id number? Is it the project key or the organisation key or is it the error we received.?
This is the error we received. ✖ Quality Gate failed: Could not fetch quality gate status: b'{"errors":[{"msg":"Analysis with id \\u0027None\\u0027 is not found"}]}'
Hi,
This is the error we received ✖ Quality Gate failed: Could not fetch quality gate status: b'{"errors":[{"msg":"Analysis with id \\u0027None\\u0027 is not found"}]}'
I’m not finding a good example of how this is supposed to be configured (I’ll bring that up internally) but I believe you’re getting the error on the Quality Gate pipe because the working assumption is that the QG pipe will access data from the Analysis pipe to get that analysis id.
Can you put both pipes in the same script? I don’t have experience with Bitbucket, but the internet is telling me it’s possible to do that.
Over 200 repositories currently use this pipeline, and it functions perfectly. This pipeline was also operating properly just a few days ago, but for some reason—which is unknown to us—it suddenly generated this error.