GitLab vs Travis CI comparison

"The most important features of GitLab for us are issue management and all the CI/CD tools. Another aspect that I love about GitLab is the UI."

"The stability is good."

"They incorporate new features every September, and they have introduced their own code editor and AI features."

"I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently."

"The most valuable feature of GitLab is its convenience. I am able to trace back most of my changes up to a far distance in time and it helps me to analyze and see the older version of the code."

"When a developer checks in code, it is automatically built and deployed, and automated test cases are also run. We have extensive integration with GitLab, which helps us with source code management. We run the static code analysis using SonarQube."

"GitLab is very well-organized and easy to use. Also, it offers most features that customers need."

"The dashboard and interface make it easy to use."

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

"I would like to have some features to support peer review."

"GitLab could improve by having more plugins and better user-friendliness."

"Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict."

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

"We would like to generate document pages from the sources."

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

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

"The documentation is confusing."

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

"This is an open-source solution."

"The solution is free."

"As I work in a vast enterprise, I'm unsure about the licensing cost for GitLab. It's the management team that takes care of that."

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

"I'm not sure if they have some kind of discount. I've been negotiating with them on prices before, and I believe they weren't too happy to give discounts, but list prices are $19 per user, per month for Premium and $99 per user, per month for Ultimate. So, the difference between Premium and Ultimate is a bit bigger, and in most companies, you need to build some type of business case."

"The solution is based on a licensing model that includes technical support and is paid annually."

"The solution is based on a subscription model and is reasonably priced."

"The solution's pricing is acceptable."