We performed a comparison between GitHub Actions and Jenkins based on real PeerSpot user reviews.
Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The level of automation achievable is really good. So, the custom workflow creation and Marketplace Actions improved our project's efficiency."
"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."
"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 just 8 to 10 minutes through these optimizations."
"It offers numerous built-in features for pipeline management, release management, and even work item tracking on boards, which makes it a versatile tool that seamlessly integrates with hardware and facilitates optimization."
"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 most valuable feature of the solution is that it is a good product that offers stability and performance."
"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."
"The most valuable features of Jenkins are the integration with GitHub, and the automation for deployment."
"Has a good interface, is reliable and saves time."
"It has a lot of community posts and support."
"Very easy to understand for newcomers."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"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 reporting capabilities are somewhat limited."
"The UI could be better."
"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."
"There is a part that detects outdated libraries. If that feature could be more intuitive and informative, that would be nice."
"The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
"For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"The documentation on plugin development could be better: more examples. "
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"Support should be provided at no cost, as there is no free support available for any of the free versions."
"The scriptwriting process could be improved in this solution in the future."
"Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable."
GitHub Actions is ranked 7th in Build Automation with 6 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. GitHub Actions is rated 8.4, while Jenkins is rated 8.0. The top reviewer of GitHub Actions writes "Facilitates connectivity for developers and allows us to easily collaborate with other developers, regardless of location". On the other hand, the top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". GitHub Actions is most compared with Tekton, Bamboo, AWS CodePipeline, GitLab and Harness, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Tekton. See our GitHub Actions vs. Jenkins report.
See our list of best Build Automation vendors.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
