GitLab vs Jenkins vs Travis CI comparison

"CI/CD and GitLab scanning are the most valuable features."

"GitLab has better support, and its features are superior compared to Jenkins."

"Of all available products, it was the easiest to use and easy to install."

"CI/CD is valuable for me."

"We have seen a couple of merge requests or pull requests raised in GitLab. I see the interface, the way it shows the difference between the two source codes, that it is easy for anyone to do the review and then accept the request; the pull request is the valuable feature."

"I recommend GitLab for DevOps engineers."

"It speeds up our development, it's faster, safer, and more convenient."

"The most valuable features of GitLab are the review, patch repo, and plans are in YAML."

"Jenkins has built good plugins and has a good security platform."

"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."

"Jenkins has excellent task planning features."

"It's very useful when you want to automate different processes from beginning to end."

"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."

"The automated elements are easy to use and you can put them into your server."

"The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions."

"We used it for all continuous integration parts, like automation testing, deployment, etc."

"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."

"I used Spring Cloud config and to connect that to GitLab was so hard."

"The solution could be faster."

"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."

"I rate the support from GitLab a four out of five."

"As a partner, sometimes it's difficult to get support. They have a really complicated procedure for their support."

"Technologies are always changing. Nowadays, new things like serverless computing and workload management have emerged. We have noticed a few gap items for faster service delivery. For example, we do user interface testing in the latest team and automate it using some tools. Recently, we integrated a tool with user interface testing, which can simulate a multi-user environment. So, we would like to see more integration with different platforms."

"It would be really good if they integrated more features in application security."

"I don't really like the new Kubernetes integration because it is pretty focused on the on-premise environment, but we're in a hybrid environment."

"The major drawback with Jenkins is the lack of support."

"There are some difficulties when we need to execute the DB script."

"Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly."

"We need more licensed product integrations."

"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."

"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."

"Jenkins could improve the integration with other platforms."

"The documentation is not helpful, as it is not user-friendly."

"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."

"Its price is fine. It is on the cheaper side and not expensive. You have to pay additionally for GitLab CI/CD minutes. Initially, we used the free version. When we ran out of GitLab minutes, we migrated to the paid version."

"It is very expensive. We can't bear it now, and we have to find another solution. We have a yearly subscription in which we can increase the number of licenses, but we have to pay at the end of the year."

"We are using the free version of GitLab."

"In terms of the pricing for GitLab, on a scale of one to five, with one being expensive and five being cheap, I'm rating pricing for the solution a four. It could still be cheaper because right now, my company has a small team, and sometimes it's difficult to use a paid product for a small team. You'd hope the team will grow and scale, but currently, you're paying a high license fee for a small team. I'm referring to the GitLab license that has premium features and will give you all features. This can be a problem for management to approve the high price of the license for a team this small."

"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a five out of ten."

"We are using its free version, and we are evaluating its Premium version. Its Ultimate version is very expensive."

"The price of GitLab could be better, it is expensive."

"The solution's pricing is acceptable."

"We are using the freeware version of Jenkins."

"Some of the add-ons are too expensive."

"Jenkins is not expensive and reasonably priced."

"The open-source version is free, but small companies would not be able to afford the cloud-based version."

"Jenkins is open source."

"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."

"The solution is one of the lowest costs compared to competitors."

"It is an open source."