Hi Ann, the plugin issue is just 1 part of the real issue, when the job fails, Sonar Qube performance decreases a lot, having jobs to actually take 2x-4x times the scan time, we couldn’t see any evident issues on the Cloud side, neither on the Sonar Qube server, but we have seen some errors with the database connectivity, so we need to clear out with your team that the setup done for SonarQube is correct, we followed the recommendations made by our Product Manager, however, that documentation doesn’t include specifics in terms of IOPS (it just says it must be high, but what is high?), what is the VM size recommended for Azure? Also, there is no specification for the database requirements, based on the database errros we saw, is this being a problem? Does the Database have to be in a nodepool? What is the expected database utilization? What is the database recommendation for azure?
Last but not least, Java heap, workers and swap, do you have a recommendation for this? The documentation found online really doesn’t explain much and mentiones how carefull you must be to even modify some of the values cause it could really cause more problems that it will fix.
Going back to the plugin issue, this is faced just before the performance issues start, however, this is not constant, I had a Jenkins running 2 scans every 4 minutes (1 every 2 minutes), 1 of them going directly to the VM and the other going through the internet and then the Application Gateway, and only 1 job out of around 1000 jobs failed due to the plugin issue, and then the time duplicated.
We also need to know if there are ways to speed up or improve the scans through the project scan declaration, as this is affecting 1 team in specific and it is really breaking things around their DevOps pipelines.
Please walk us through any required logs or specific information you need to find out the possible cause of the issues we are facing.