We performed a comparison between GitHub Actions and GitLab 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 most valuable feature of the solution is that it is a good product that offers stability and performance."
"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 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."
"The level of automation achievable is really good. So, the custom workflow creation and Marketplace Actions improved our project's efficiency."
"It scales well."
"The most valuable functionality of GitLab, for me, is the DevOps. Besides the normal source control based on Git, I find the Auto DevOps features most important in the solution."
"GitLab is being used as a repository for our codebase and it is a one stop DevOps tool we use in our team."
"Their CI/CD engine is very mature. It's very comprehensive and flexible, and compared to other projects, I believe that GitLab is number one right now from that perspective."
"This product is always evolving, and they listen to the customers."
"The solution is stable."
"I have found the most valuable features of GitLab are the GitClone, GitPush, GitPull, GitMatch, GitMit, GitCommit, and GitStatus."
"The tool helps to integrate CI/CD pipeline deployments. It is very easy to learn. Its security model is good."
"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 reporting capabilities are somewhat limited."
"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 solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly."
"As GitLab is not perfect, what needs improvement in the solution is the Wiki feature of the groups or the repertories because currently, it's not searchable by default. You'll need an indexing service such as Elasticsearch to make it searchable, and that requires too much work, so for me, it's the main feature that should be improved in GitLab. In the next version of the solution, from the top of my head, the documentation could be improved. Besides the Wiki, it would be good if there's documentation that would be automatically generated based on the code repository. In other words, there should be some tutorials from GitLab for developers in the next release."
"GitLab doesn't have AWS integration. It would be better to have integration with other container management environments beyond Kubernetes. It has very good integration with Kubernetes, but it doesn't have good integration with, for example, AWS, ETS, etc."
"As a partner, sometimes it's difficult to get support. They have a really complicated procedure for their support."
"GitLab can improve the integration with third-party applications. It could be made easier. Additionally, having API control from my application could be helpful."
"GitLab can improve by integrating with more tools, such as servers with Docker."
"GitLab could improve the patch repository. It does not have support for Conan patch version regions. Additionally, better support for Kubernetes deployment is needed as part of the package."
"I've noticed an area for improvement in GitLab, particularly needing to go through many steps to push the code to the repository. Resolving that issue would make the product better. My team quickly fixed it by writing a small script, then double-clicking or enabling the script to take care of the issue. However, that quick fix was from my team and not the GitLab team, so in the next release, if an automatic deployment feature would be available in GitLab, then that would be good because, in Visual Studio, you can do that with just one click of a button."
"Perhaps the integration could be better."
GitHub Actions is ranked 7th in Build Automation with 6 reviews while GitLab is ranked 1st in Build Automation with 70 reviews. GitHub Actions is rated 8.4, while GitLab is rated 8.6. 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 GitLab writes "Powerful, mature, and easy to set up and manage". GitHub Actions is most compared with Tekton, Bamboo, AWS CodePipeline, Harness and TeamCity, whereas GitLab is most compared with Microsoft Azure DevOps, Bamboo, SonarQube, AWS CodePipeline and Tekton. See our GitHub Actions vs. GitLab 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.
