Harness vs Klocwork comparison

"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place, making it convenient."

"It's a highly customizable DevOps tool."

"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."

"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."

"Harness starts integrating with organizations, making everything automated without the need for manual interruption."

"It's integrated into our CI, continuous integration."

"On-the-fly analysis and incremental analysis are the best parts of Klocwork. Currently, we are using both of these features very effectively."

"There is a central Klocwork server at our headquarter in France so we connect the client directly to the server on-premises remotely."

"The most valuable feature is the Incremental analysis."

"The ability to create custom checkers is a plus."

"One can increase the number of vendors, so the solution is scalable."

"The most valuable feature of Klocwork is finding defects while you're doing the coding. For example, if you have an IDE plug-in of Klocwork on Visual Studio or Eclipse, you can find the faults; similar to using spell check on Word, you can find out defects during the development phase, which means that you don't have to wait till the development is over to find the flaws and address the deficiencies. I also find language support in Klocwork good because it used to support only C, C++, C#, and Java, but now, it also supports Java scripts and Python."

"Technical support is quite good."

"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."

"I prefer the previous less compact UI version of Harness, which showed more details on the screen."

"Even with automation, there's a requirement for manual change requests for approvals."

"When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment."

"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."

"The main problem is that since it only parses the code, the warnings or the problems that are given as a result of the report can sometimes require a lot of effort to analyze."

"Now the only issue we have is that whenever we need to get the code we have to build it first. Then we can get the report."

"There are too many warnings, and it requires expertise to determine the correct category for them."

"Modern languages, such as Angular and .NET, should be included as a part of Klocwork. They have recently added Kotlin as a part of their project, but we would like to see more languages in Klocwork. That's the reason we are using Coverity as a backup for some of the other languages."

"Klocwork sometimes provides too many additional warnings which require expertise to manage."

"We'd like to see integration with Agile DevOps and Agile methodologies."

"I would like to see better codes between projects and a more user-friendly desktop in the next release."

"Every update that we receive requires of us a lengthy and involved process."

"Klocwork is still tight on their licensing. If Klocwork would loosen up on the licensing, and where the license could be used, and how many different programs could be run on it, then we have several development programs that I would love to be able to use it for going forward."

"The limitation that we have is that Klocwork is licensed to certain programs, and if you want to license them to other programs, you have to pay more money."

"There are other solutions on the market such as Microsoft Visual Studio. They have been adding more static code analysis features that come for free. It is getting better all the time. That is one of the possibilities is that we've been considering that we may stop using the Klocwork because it doesn't give us any added value."

"Licensing fees are paid annually, but they also have a perpetual license."

"The pricing for Klocwork is very competitive if you compare it from apple to apple. It has competitive pricing regarding the licensing model and the per-license cost. Klocwork isn't a high-end investment for anyone deploying it; even SMBs can afford it. The Klocwork cost per user would depend on the license type, so I'm unable to mention a ballpark figure because it would depend on the type of installation and how the deployment will be, and the nodes to give an accurate calculation or figure. The total price depends on the package, so my company could never publish pricing for Klocwork on the website. My team first collects information from potential clients on the deployment scenario, project environment, etc., before suggesting a package for Klocwork. My rating for Klocwork in terms of pricing is a five because of its flexible license models. There's a license model for every type of organization, whether small, midsize, or enterprise, so it's a five out of five for me."

"Klocwork should not to be quite so heavy handed on the licensing for very specific programs."

"This solution offers competitive pricing."

"When it comes to licensing, the solution has two packages, one for a fixed and the other for a floating server, with the former being more cost effective than the latter."