The tool is very stable. I rate the stability an eight out of ten.

Because we are using in-house tools, it's a little bit unstable.

I would rate its stability capabilities eight out of ten.

Jenkins is a stable product.

The solution is stable.

If there isn't any problem with the server where Jenkins is installed, I don't have any issues with Jenkins. We have had to restart it a few times to free up memory, but we run it on a multi-node cluster. That helps because we can redirect traffic through one of the servers while we restart the other. Some minor restarts need to be done to free up memory, but we have redundancy in place so it doesn't affect the system availability.

Jenkins is a stable solution.

Stability-wise, it's a pretty decent tool. Basically, It's an average product. So, I won't rate it the best or worst, as it's somewhere in the middle. If I was given to choose a better deployment service, I would definitely use that service rather than using Jenkins. I rate the solution's stability a six out of ten.

The solution is stable. We haven't had any real issues. There are no bugs or glitches. It doesn't crash or freeze. 

I wouldn't call Jenkins rock solid. It certainly requires ongoing administration.

The solution is stable.

The solution is stable but it is slow. It is a free service so I can't complain about the time it takes.

The solution is stable. It's reliable. There are no bugs or glitches and it doesn't crash or freeze.

The solution is stable. However, if you have any network interruption or any server failure it will not be stable.

We have found the stability of this solution to be good.

I rate Jenkins' stability a six out of ten. 

The solution is stable. Sometimes the host server may be down. However, most of the time, it's stable. 

I'd rate the stability nine out of ten.

On a scale from one to ten, I would rate Jenkin's stability at three.

Jenkins is stable.

Jenkins is a stable product.

The solution has been very stable. There are no bugs or glitches. it doesn't crash or freeze. 

In some cases, it is a very reliable solution and tool. We had some dependencies, however, we have another solution for those dependencies. Whenever we do not have any dependencies somewhere else, we can use Jenkins.

Stability is not top notch but it's pretty good. 

I would rate the stability a ten out of ten. I didn't face any crashes. It is hundred percent stable. 

The stability is good. it's reliable. I'd rate the stability four out of five. 

This is generally a stable solution. Sometimes we have experienced some issues but they have been minor. 

Jenkins is highly stable. 

Jenkins' stability is good, and we haven't had any issues with downtime.

We haven't had any problems with stability, even when we're running multiple builds. We use the product on a daily basis and although it doesn't require maintenance, there are some regular activities carried out by Jenkins every few months. 

I would rate the product a nine out of ten. 

The stability of Jenkins is good.

Jenkins is a stable solution.

It's quite stable and pretty reliable.

It is very stable.

It has been pretty stable. We haven't faced any issues. If you are running Jenkins in any lower hardware, or your machine or hardware is not that compatible, you might see some memory or Java issues. If you are running Jenkins in a good hardware environment, you don't see any problem. When you have the right hardware and proper memory, there is no problem.

No issues.

Jenkins is a stable product.

Jenkins is not always stable. We have encountered approximately 20 percent downtime.

We have found Jenkins to be very stable.

Jenkins is stable.

The default settings do not work properly on Mac OS X. You have to tweak JVM parameters and allocate more heap memory as well as change other parameters to have a stable Jenkins server.

This is a stable solution. We are a team of 25 people, all working with Jenkins in some way or other, whether it's the finance data adapter or the magnet platform, which is totally Java-based and uses Jenkins. We have mainly software engineers and a few business analysts on the team. We also have a maintenance team that deals with any issues that come up.

It is a stable solution.

There are some minor bugs with this solution, but overall the stability is ok.

The solution is stable.

There have been no crashes. I would say that the only important thing is downtime. Since it is a double application, the reboot takes a long time. It would be nice if it took less time to boot. Sometimes it takes around 5 to 10 minutes to boot with all the plugins. It would be great to reduce the maintenance time so that the developers don't even notice when it has been updated. But when we update, we need to announce downtime for that.

Jenkins is as stable as the public cloud. 

The product is stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

Jenkins is stable. It provides all the required features for stability, such as backups.

The stability of Jenkins has been good in my usage.

No, although in some scenarios memory use can bloat over time.

Occasional technical glitches after upgrades.

No issues encountered.

Jenkins has been stable in my usage. However, I have had colleagues say they have had stability problems. They experienced these problems after six months to a year of use.

Jenkins is very stable.

From time to time Jenkins experiences problems after 1-2 weeks of intensive work (where at least 1-2 jobs are running at any point of time).

There used to be some issues when entire configurations could become invisible from the UI (usually that could happen after unexpected system shut down or even simple configuration rename operation) which was a bit painful. But I didn't encounter such problems in the most recent versions. So, it definitely indicates that some work at this direction was definitely done.

Jenkins works perfectly well - we've never faced any outages or issues with it.

No stability issues.

No issues encountered.

Rarely. I can remember only one time we lost our build info after upgrading Jenkins, somewhere around the 1.6xx versions.

Sometimes you have Jenkins restarting because of OOM errors.

With few plusgins, like Monitoring. it crashes.

 It is stable.

The solution is stable.

For automation tests, Jenkins nodes some times experience instability. I have no better solution yet, since I have concerns with the networking and firewall as well.

Some plugins have critical bugs and are not able to be used.

When there is enough disk space and RAM, the solution is stable.

Minor, but those issues typically gets fixed after reporting them. Some issues can be addressed as pull requests, fixing them myself.

I would say it's a quite stable system.

Sometimes, out-of-memory problems, but lately this has not occurred often. Sometimes there are obscure Java errors which are hard to understand.

There were some issues with stability.

Yes, in Jenkins v.2. However, I am guessing that is because we used it right after the first release.