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

CloudBees vs GitHub Actions comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

Review summaries and opinions

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

Categories and Ranking

CloudBees
Ranking in Build Automation
6th
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
20
Ranking in other categories
Configuration Management (11th), Value Stream Management Software (2nd), DevSecOps (4th)
GitHub Actions
Ranking in Build Automation
4th
Average Rating
8.4
Reviews Sentiment
7.6
Number of Reviews
21
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2025, in the Build Automation category, the mindshare of CloudBees is 1.4%, up from 0.2% compared to the previous year. The mindshare of GitHub Actions is 11.5%, up from 6.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

YashBrahmani - PeerSpot reviewer
Offers a clear visualization and overview of workflows and helpful in managing CI/CD processes
Improvement in the sense that they can do better in terms of management of logs and stuff like that because the console logs are very extensive, and that causes a lot of storage issues. That is one of the things which is there. Also, with respect to the traditional platform and the modern platform, many things have upgraded, and it has quite improved. But when we talk about the performance of the agents, it’s still very crucial because it’s not up to par. It takes a lot of time to provision the agent and to finish the build because of the SSH connection and the JNLP connection. Due to that, sometimes the agent doesn’t get provisioned. Those are some of the blockers that meet up the time in terms of administering the instance.
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.

Quotes from Members

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

Pros

"CloudBees is the Jenkins tool for building and deploying. There's open-source Jenkins, which is free and can be used by any organization, but it offers a different architecture for Jenkins. If your organization is larger, you might choose the architecture. This way, you can have different masters for different applications, and different teams can manage their masters separately. However, a single person can still control all the masters, whoever manages it for the organization."
"It’s a very good tool for auditing your project pipelines as well."
"The security audit product offered by CloudBees is particularly beneficial in automating audit processes, which reduces the time developers spend on audits."
"The initial setup is easy."
"CloudBees operates seamlessly. Deploying to a cluster is straightforward—just one click, and the job is done."
"The most valuable feature of the solution is that its GUI is quite simple."
"CloudBees assists by automating tasks, previously done manually, in the pipeline setup."
"CloudBees updates its features frequently, so if we need something like SSL login, they enable it."
"I am familiar with the entire life cycle of the product."
"The product's most beneficial feature is the ability to create workflows within the solution."
"The most valuable features of GitHub Actions include its seamless integration within GitHub, which simplifies the CI/CD pipeline setup. The scalability of using different types of runners—both public and private runners—enhances deployment flexibility."
"It is user-friendly, with clear and organized processes, making it easy to navigate and work with."
"GitHub Actions is a beautiful tool that integrates smoothly with all major tools, reducing CI/CD work by 30% to 40%."
"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."
"The main benefit is collaboration. It allows us to easily collaborate with other developers, regardless of location. For example, we can collaborate with both our African and German colleagues seamlessly. It's platform-agnostic, so it is flexible and not tied to any OS, so we can work on Linux, Windows, web, and even Oracle applications. It's flexible, reliable, and overall an excellent tool for our needs."
"The most valuable feature of the solution is that it is a good product that offers stability and performance."
 

Cons

"To use the tool, you need to be familiar with the tool itself and with how it will be incorporated into the culture."
"I would like to see improved speed and availability."
"It could improve the document upload process."
"We did face some challenges, particularly with the infrastructure."
"One challenge I'd like to highlight is that with CloudBees CI growing bigger and bigger, there are limitations in terms of managing old plugins and services and upgrading them with time."
"The platform could integrate better with other tools and support external tools directly."
"The setup is somewhat complicated. You need a cloud architect and engineer to set it up properly. The initial setup will take time, so you need a good engineer and architect to handle it."
"I think a preview of the errors would be good just at the point where the error occurs."
"The only issue I have faced is with authorization, particularly when configuring the GitHub token correctly."
"The reporting capabilities are somewhat limited."
"There is a part that detects outdated libraries. If that feature could be more intuitive and informative, that would be nice."
"The UI could be better."
"GitHub Actions lacks a feature for automating the build process for mobile applications."
"The main challenge I've experienced is with integration, particularly uploading to OneDrive, which was more complex compared to Google Drive or AWS S3 bucket."
"The main improvement would be to add support for more programming languages and frameworks."
"In terms of improvements, I think better logging for debugging purposes would be helpful, especially for complex workflows."
 

Pricing and Cost Advice

Information not available
"It's low-priced. Not high, but definitely low."
"It is free and open platform, so I would rate it 1 out of 10."
"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."
"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."
"For our basic usage, we didn't have to pay."
"The product is slightly more expensive than some alternatives."
"The cost for GitHub Actions may be around $45 dollars per user."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
860,168 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
25%
Manufacturing Company
12%
Legal Firm
11%
Computer Software Company
8%
Financial Services Firm
17%
Computer Software Company
11%
Manufacturing Company
11%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with CloudBees?
There are connection issues with CloudBees, specifically between Sybase and CloudBees. We often encounter connection problems, and there are issues with the pipelines.
What is your primary use case for CloudBees?
We use CloudBees for deploying the code in higher environments, such as QA, C2, staging, and production.
What advice do you have for others considering CloudBees?
I would recommend CloudBees to others because building jobs is much easier than with other solutions.
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?
I would rate pricing a seven, which leans toward the expensive side. However, there is still value for money, and that's why we continue using it.
What needs improvement with GitHub Actions?
I would need to check with my team about specific shortcomings. We still use Jenkins ( /products/jenkins-reviews ) for some tasks, which suggests there may be areas for improvement in GitHub Actions.
 

Comparisons

 

Overview

 

Sample Customers

Capital One, PEGA, vistaprint, HSBC, BOSCH, Starbucks Coffee
Information Not Available
Find out what your peers are saying about CloudBees vs. GitHub Actions and other solutions. Updated: June 2025.
860,168 professionals have used our research since 2012.