The solution's stability is good. I rate the stability an eight out of ten.

It's a stable solution.

The stability is very good. 

Any lack of stability is because it's being expanded and updated pretty much constantly. We haven't experienced any crashes or bugs. We do have an opportunity here coming up within the next few weeks of revisiting some of the ways we do things there.

I rate the tool’s stability a nine out of ten.

I would rate the stability of the solution as an eight out of ten.

The stability is fine. With any software, you must ensure that you keep up to date with the software. As a result, when there are new ways to attack you, the software detects it. You must be prepared. You can't just put it in and forget about it, you have to stay current.

The solution is stable.

It is a stable solution. So, no issues with stability.

The solution is stable. 

We are not relying on this solution as a go-to application security scanning tool. We use it for some minor enhancement regarding security, but we are using it actively in other departments for the code quality scanning. I have not had any problems using the solution, it has been stable.

I rate the stability an eight out of ten.

It is a stable product. I rate it seven out of ten.

The product is stable although maintenance is a little cumbersome. 

I would rate the stability a ten out of ten. 

We haven’t faced any issues with the solution’s performance or stability.

I have not faced any issues with stability so far.

SonarQube is a reliable solution.

The dimensional stability of the impression materials depends on the time elapsed between the completion of the impression and their casting, thus storage time is critical to obtaining reliable casts.

This solution consumes resources but that's something that is needed. In terms of performance, it's okay. It depends on the power of the hardware and servers that you have.

This is a product that we use on a daily basis. We are constantly developing software and this is used as part of the process.

The solution is quite stable. Before, I used to generate reports by using some manual techniques. Now those are available right in SonarQube. The flexibility of rule configurations is great.

It is very stable. We are still new to this product and learning, but there are times where SonarQube disconnects from the server with no alert or notification, and we have to run it again.

It can be managed by running different scripts. From time to time we have claims that SonarQube is not running on the server and discovered that the server was restarted but SonarQube did not restart.

I don't know if it is a flaw in the product itself or if we can manage it from our infrastructure.

It's stable but could be improved.

It is stable in the system environment processes.

It is quite stable. There are no kind of issues that we face on SonarQube. It's just about the awareness where the users are not aware of a feature and that's where we need to jump in and explain some of the features about how it works.

This solution is very stable.

This is a stable solution. 

The stability and performance of SonarQube are good. We use it on a daily basis, as part of our code development. 

As far as maintenance, it mainly happens when the product is being developed. There may be some features which can be enhanced, based on customer feedback and the tech stack, such as how we can improve performance of have a deployment with zero downtime. There are so many technologies coming, so many things happening, and there is always room for code improvements and the product we develop. Our top considerations are quality and security, which are being improved in a continuous process. There are many new features and enhancements coming in—for example, if you want to upgrade from the Java 6 version, then you can upgrade the tech stack, which will reduce the number of lines of code and improve performance. 

Good, I have not really had many issues with it. No major ones either. 

We use C++ and a lot of Python. Another group in our company is using Java. SonarQube is more directly suited for Java, being almost built into it, whereas C++ requires some extensions. The Java group is using a newer version. We were kind of hoping to piggyback on theirs but SonarQube did not create newer versions of the C++ interfaces as open source. It's starts costing money so we haven't crossed that threshold yet. We haven't established a clear path.

SonarQube is a stable solution.

The stability of this solution is quite good.

I rate the solution a seven out of ten for stability.

The solution is stable.

I have not run into any bugs or glitches. However, I have only been using it for a short time.

It is stable.

We have not found any bugs or had trouble with stability. We have had some minor hiccups, here and there, but otherwise, we are fine.

The stability of SonarQube is good.

The solution is quite stable. 

The stability is good. 

The branch advanced analysis pull request declarations, they are good and highly valuable, but they are not part of the free edition. They are only available as part of the licensed one.

SonarQube is a highly stable solution.

I have not faced any bugs or glitches in SonarQube.

We have been using this for quite a number of applications, and its stability is very good. The scan time is very fast because it is a text-based scan.

It seems to be very stable. I haven't had many issues with it. 

We just upgraded to the 6.7 version, which has been performing well.

The tool is stable. 

Its stability is very good.

We have only used this solution for a few weeks, but so far we have had no issues at all.

I rate the tool's stability a six out of ten. 

The solution is quite mature. We did not have many issues.

SonarQube is quite good in terms of stability.

There can be some stability issues.

SonarQube stability is fine. I would rank it high on the stability side.

There were initially some questions about performance and in particular the location of the database (some suggesting that this needed to be physically close to the point of analysis to minimize network latency). However, this is highly dependent on the size of the code base under analysis (and the multiplicity of code bases). In our case we didn’t find any problem in running the database, server and analysis process in separate locations (RDS, EC2 and Jenkins respectively). Our largest code base to-date is around 500K lines.

The stability is good. We are not having problems with the product failing.  

I haven't had any issues with stability and we see it as quite stable.

The only time we had an issue was because we used a third-party plugin for it to integrate with another piece of software and there was a versioning issue. Other than that, we haven't had any trouble. We've had to integrate it with our LDAP and everything seems to run quite smoothly.

It seems a lot more stable in the current versions of the product. I have never had major issues though, so I would say it's pretty stable.

The solution is pretty much stable. Sometimes we have observed some issues when there are a lot of services getting deployed together. We have noticed some resource constraints sometimes. Occasionally the CPU and memory get affected. That was the only thing. It could be due to the resources that we have provided and maybe not the fault of the product itself.

No.

So far, we are happy and haven't had any issues with stability.

The only maintenance this product needs, for now, is just updates and patches. 

SonarQube is an auditing requirement from our side and for our SDLC, so it is a gate in our SDLC. 

A single developer claimed that the SonarLint plugin caused performance issues on his IntelliJ IDEA. However, this issue was not encountered by the other developers.

No issues encountered.

This is a stable solution. 

This solution is stable. Stability is not an issue for us.

The SonarQube is stable.

It looks stable. So far, we haven't found any issues.

SonarQube is stable.

SonarQube works very well, but I prefer SonarCloud because the tendency of the technology world is to think less about the structure and more about the process and the value that this process provides.

I didn't encounter any issues with stability.

This is a stable solution.

There were no stability issues. I can't think of any serious issues.

Once it is up and running, we didn't find any big issues with the stability, but it's important to configure in the right way the properties file according with you system specifications.

I don't think I ever had a problem.

The solution is stable.

There are issues with stability. It needs improvement.

We have four members in our organization who are using this solution.

SonarQube is a stable solution.

The stability is good.

This is a stable solution.

I have not encountered any issues.

The stability is good.

The solution is very stable. We don't have any issues with its reliability. It's been quite good so far.

The product is stable.

Stability has never been a problem. It would have to be unstable for me to experience a problem, and we haven't. So it's good.

We are using everything that is open-source and this allows us when we have the regular day to day issues, our team works on them directly to identifying their causes and they resolve them quickly.

I have not seen any problems in terms of stability, although it has not been onboarded yet. Once that happens, we may see more problems.

No issues encountered.

It is stable.

I have not run into major issues or bugs and it works well when it comes to stability.

We had some stability issues where the Quality Gate check sometimes got stuck and it was unclear. This seldom happens.

In terms of stability, the solution is reliable and the performance is good. There are no bugs. It's not glitchy. It doesn't crash or freeze. 

It is stable.

Only common issues have been experienced.

No issues encountered.

No.

The stability is good.

The stability is good.