Try our new research platform with insights from 80,000+ expert users

GitHub Actions vs Harness comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

GitHub Actions
Ranking in Build Automation
5th
Average Rating
8.4
Number of Reviews
15
Ranking in other categories
No ranking in other categories
Harness
Ranking in Build Automation
12th
Average Rating
7.6
Reviews Sentiment
8.1
Number of Reviews
2
Ranking in other categories
Static Application Security Testing (SAST) (30th), Cloud Cost Management (15th)
 

Mindshare comparison

As of November 2024, in the Build Automation category, the mindshare of GitHub Actions is 10.1%, up from 1.2% compared to the previous year. The mindshare of Harness is 5.0%, up from 4.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

MohamedMostafa1 - PeerSpot reviewer
Handles scalability well, automatically managing execution infrastructure without requiring additional configurationsThe automation feature of GitHub Actions is
I find the automation feature of GitHub Actions most valuable for our building processes. It integrates seamlessly with GitHub, so there's no extra configuration needed, making the building process easy and efficient. GitHub Actions handles scalability well, automatically managing execution infrastructure without requiring additional configurations. We haven't yet explored GitHub Actions' support for AI projects, as we haven't used its AI capabilities.
Misbah Mohammed Kollathodi - PeerSpot reviewer
Provides a good graphical interface, but the initial setup process needs improvement
The platform's initial setup process could be simplified. Additionally, security features and capabilities for understanding vulnerabilities within the application could be enhanced directly from the tool. There's also room for improvement in debugging pipeline issues, which can sometimes become complex. Limitations regarding reconciliation features and support for certain parts of the infrastructure should also be addressed.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The level of automation achievable is really good. So, the custom workflow creation and Marketplace Actions improved our project's efficiency."
"GitHub Actions is valuable for its ease of use and integration."
"Creating workflows in YAML format is straightforward and easy to comprehend. This includes both understanding and writing workflows. Additionally, the downloading aspect for third-party instances can also be easily done. It's worth noting that vulnerability analysis and similar tasks should be part of our automation through data workflows. Furthermore, we can break down our processes step by step, starting from building, then moving on to analysis, testing, and finally deploying in production and the clear environment. All of these tasks can be efficiently managed within this platform."
"I find the automation feature of GitHub Actions most valuable for our building processes. It integrates seamlessly with GitHub, so there's no extra configuration needed, making the building process easy and efficient. GitHub Actions handles scalability well, automatically managing execution infrastructure without requiring additional configurations. We haven't yet explored GitHub Actions' support for AI projects, as we haven't used its AI capabilities."
"It is user-friendly, with clear and organized processes, making it easy to navigate and work with."
"The most valuable feature of the solution is that it is a good product that offers stability and performance."
"It is a very stable solution as we have not faced any issues."
"GitHub Actions can be easily configured, especially for environment variables and secrets. The UI is understandable and user-friendly for setting up CI/CD pipelines. I prefer tools like GitLab, where the pipeline starts quickly and is accessible near the commits for easy access. However, many CI/CD tools are interchangeable due to similar features of GitHub Actions and other similar tools."
"It's a highly customizable DevOps tool."
"Harness starts integrating with organizations, making everything automated without the need for manual interruption."
 

Cons

"The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly."
"GitHub sometimes makes it difficult to debug actions."
"There is a part that detects outdated libraries. If that feature could be more intuitive and informative, that would be nice."
"We can leverage this database tool to manage everything within our environment and data burners, allowing for customization and execution. An additional advantage is the capability to modify aspects like file size, making processes more efficient and faster across the pipelines. Regarding improvements or implementations, I believe there should be enhancements made to the deployment tool. It should be integrated as part of the solution. Infrastructure-wise, we already have tools like GitHub and RobSpot, and data enables us to automate various processes, which is quite beneficial. As for further enhancements, I'm uncertain. I've shared everything I know. However, if there's something specific you'd like to see in future releases, a feature that may not exist yet but would be desirable, I can't provide any input on that matter."
"The only issue I have faced is with authorization, particularly when configuring the GitHub token correctly."
"The reporting capabilities are somewhat limited."
"The primary area for improvement I see is in artifact management, especially for saving screenshots or videos from failed tests or data-driven actions. Currently, the configuration for saving these artifacts is complex."
"In terms of improvements, I think better logging for debugging purposes would be helpful, especially for complex workflows."
"Even with automation, there's a requirement for manual change requests for approvals."
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."
 

Pricing and Cost Advice

"It's low-priced. Not high, but definitely low."
"Price-wise, GitHub Actions is okay. If I want to use the product's advanced features, then I need to pay the licensing charges for the solution."
"For our basic usage, we didn't have to pay."
"It is free and open platform, so I would rate it 1 out of 10."
"The product is slightly more expensive than some alternatives."
"The tool's price is okay and reasonable."
"Regarding cost, as an enterprise, we negotiate our license and expenses, so I can't provide a specific rating for that."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
13%
Manufacturing Company
12%
Healthcare Company
7%
Financial Services Firm
35%
Computer Software Company
13%
Government
6%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about GitHub Actions?
I have optimized job execution time by running test scripts in parallel and creating multiple pipelines; we've significantly reduced execution times. What could take 50 minutes can be cut down to j...
What is your experience regarding pricing and costs for GitHub Actions?
The solution is open source, making it cost-effective for individual users. However, company usage may depend on its scale and specific requirements.
What needs improvement with GitHub Actions?
GitHub sometimes makes it difficult to debug actions. Improvements in debugging could enhance its usability greatly.
What do you like most about Harness?
It's a highly customizable DevOps tool.
What needs improvement with Harness?
Even with automation, there's a requirement for manual change requests for approvals. If this is corrected, we could have a totally automated pipeline. Otherwise, we need to use GitLab or GitOps to...
What is your primary use case for Harness?
We use Harness as a deployment tool. It allows us to define environments like OpenShift or Kubernetes or Linux servers. It automates the pipeline system where users can trigger with the master bran...
 

Comparisons

 

Also Known As

No data available
Armory
 

Learn More

Video not available
 

Overview

 

Sample Customers

Information Not Available
Linedata, Openbank, Home Depot, Advanced
Find out what your peers are saying about GitHub Actions vs. Harness and other solutions. Updated: November 2024.
816,406 professionals have used our research since 2012.