External reviews are not included in the AWS star rating for the product.
GitLab serves as my main DevOps platform for managing our repository and code base, as well as for pipeline integration of our system.
We maintain all our projects in GitLab with separate folders for project files, and we use GitLab to manage our projects. We also use GitLab pipeline to deploy in our dev environment, QA environment, and production, as well as for creating patches.
GitLab has positively impacted my organization by being faster than other platforms and providing the best user interface and features. Creating merge requests is easy, and it makes it simple to use for new joiners.
GitLab's best features are its built-in CI/CD and pipeline integration, which can be easily connected to AWS or other deployment platforms. The CI/CD pipeline integration is the most valuable aspect for me, and it also provides an easy user interface to create merge requests, merge, and create branches.
The CI/CD pipeline integration has helped my workflow by allowing us to use the .gitlab-ci.yml file to integrate and write our pipeline codes, where we include build jobs, test jobs, and deploy jobs directly with our AWS for S3 using CI/CD variables for push.
In GitLab pipelines, both manual and automatic integration are offered for the pipeline runner, and pipeline logs are provided, which are very useful for DevOps engineers and developers for debugging.
GitLab can be improved by being more responsive in the UI and offering better pricing for premium features, which would be useful for small startups. While GitLab's CI/CD is powerful, it is somewhat complex in certain aspects.
It would be better if the GitLab and Jira integration were more flexible and easier to integrate with Jira for task management in the future.
Since I joined my company, we have been using GitLab for our repo maintenance, so I have been using it for more than two years.
In my experience, GitLab is stable; however, sometimes it takes much time to start the runner and gets stuck in a pending situation, possibly due to traffic issues.
GitLab handles growing workloads and users well, and its scalability is good, but the downtime issue is a concern because it sometimes takes too long to start the runner.
Earlier, I did my personal projects using GitHub before I joined my current organization, which uses GitLab, and that is the reason for switching. I personally prefer GitLab over GitHub because it is user-friendly and easy to work with.
My current organization started with GitLab.
I would advise others looking into using GitLab that it is a perfect platform for organization-level repository management and pipeline CI/CD features are very useful and easy to use.
I have shared everything I feel and noted the pros and cons of GitLab as a user. Overall, I rate GitLab positively, giving it a seven out of ten because I have been using GitLab for more than two and a half years and have not faced many difficulties. However, in some cases, I got stuck with runners getting delayed to run, which can be annoying.
To store the data.
Git merging allows us to track the details of how and who has done what. This is the best feature which is useful for all companies.
As we are using it in Kubernetes clusters, we don't have any issues.
Approximately four to five years.
Recently we had an issue where an employee left the company and their commits were erased. We raised a request with GitLab support, but they were unable to help because they could not find the root cause of what went wrong. We restored the data from previous backups.
GitLab is suitable for small and mid-size organizations, but not for enterprise use.
We raised a request with GitLab support when an employee's commits were erased, but they were unable to help because they could not find the root cause of what went wrong.
Positive
I worked with GitLab Enterprise at a previous company. GitLab Enterprise is far better than the free version. For enterprise-level customers, we can recommend GitLab Enterprise. Regarding competitors, we have explored GitHub, Bitbucket, and CircleCI. However, GitLab Enterprise has more features than any of these tools.
I am working with Kyndryl, which is part of IBM. They have their own decision-making team who manages these aspects.
We are currently using general GitLab, not GitLab Premium.
We are using Jira and Confluence, but not Bitbucket.
We are currently using GitLab integrated with Sonar for code vulnerability checks, Jenkins, Camunda, and XL Deploy. We use Camunda to deploy folders and XL Deploy for server deployment.
We are not using the security features on the GitLab side, as we use different tools for that purpose. My team is not using the GitLab merge request process, but we work on providing GitLab access for admin activities, as developers are in different teams handling development and merge requests.
We are using basic features currently, so I cannot comment on detailed functionality comparisons. Every versioning control tool provides similar basic features, and we are not utilizing the full functionality of GitLab.
The system is easy to use.
On a scale of 1-10, this solution rates a 7.
We are not using the community version of GitLab, but we are using it for ticketing and publishing the tool versioning.
The best features of GitLab are versioning and keeping track of the versions.
GitLab helps me save time and provide financial benefits, as keeping track of the updated version and the changes is money and time-saving.
GitLab has CI/CD pipeline capabilities.
I have been working with GitLab for probably six to seven years.
I am satisfied with GitLab's security, and we have not experienced any problems so far.
Regarding scalability, I did not face any issues with GitLab supporting my projects.
I have not contacted GitLab's technical support.
Neutral
I have seen benefits from using GitLab, since my directors and the team are using it, they must be happy with it.
I rate GitLab seven out of ten because nothing is perfect. I think we have to finish the conversation. I have told you what I could tell you.
My most common use cases for GitLab are development and managing repositories, primarily focused on code development work.
The features that are really useful for my use case generally include pulling, merging, and ensuring the pipeline is upright, which are very intuitive.
It helped me personally and my team to save time and money.
In terms of impact from using GitLab as an all-in-one DevOps platform, it helped with my project development life cycle.
Regarding improvements, making task management is something that GitLab can potentially make easier, similar to what DevOps or Jira does.
I have been working with GitLab for about two years.
The deployment and initial setup were not difficult for me to complete. The pipeline management was easy.
The setup process took less than an hour.
In terms of project management overall, I haven't faced any issues such as downtimes or losing the repository.
I haven't contacted technical support of GitLab.
When comparing GitLab with GitHub, I haven't really seen any noticeable difference.
I have worked with Azure DevOps before and found it really intuitive to use.
I have used GitHub and GitLab as well, and I find that they've been fairly intuitive to use.
Regarding GitLab, I purchased an enterprise license, though I'm not aware whether I or my company bought this license from AWS Marketplace or elsewhere.
I'm not aware of any integration with other tools or third-party applications.
I haven't faced any difficulties with user interface or deployment.
On a scale of 1-10, I rate GitLab an 8.
Positive
Neutral
The broad use of GitLab is for code check-ins, but I also use it for issue management and backlog management. It has integration with testing tools as well, and I utilize those features. GitLab supports code collaboration alongside issue and backlog management. Everyone within my team or pod, as we call it, can see each other's issues. The scrum master can look at the velocity and the burn-down charts.
I find all the CICD pipelines valuable, along with the simplicity it offers developers. When comparing it, certain features available in Jira are not present. Specifically, the ability to have weights at the milestone and epic levels does not exist. However, the security features are good and restrictive.
Certain features in Jira are not available in GitLab, such as the functionality to have weights at the milestone and epic levels. Hopefully, these features will be resolved with work items in GitLab. Also, if the child items are open in GitLab, closing the parent should not be allowed. While GitLab is a great tool for developers, it lacks project planner features. Roadmaps and Gantt charts in GitLab are not as advanced as in Jira, and changing start and end dates is more laborious in GitLab. Bridging the gap for project planners would make GitLab a more complete tool.
I have been using it for about a year.
I have not really encountered stability issues. I would rate it probably an eight.
I would say the solution is easy to scale.
I do not have direct contact with customer service. We have relationship managers who deal with GitLab directly.
Neutral
The initial setup was relatively easy.
In my company, the number of users is around ten thousand. If we are talking about my project, the figure is probably more around the three hundred mark, but it will grow to about six hundred users. In my company, that figure would be anything between five and ten thousand people.
I would rate it an eight out of ten. Also, maybe, if GitLab is supporting any AI-driven projects or if it has any automation elements, it supports them. We have AI-driven projects where the code is stored in GitLab. GitLab Copilot is something we are looking to introduce soon. If you want to maintain your issues in GitLab and raise your book of work and features, then GitLab is a great tool for collaboration and integration with code deployment and CICD pipelines.
The CI/CD pipeline with Helm has significantly improved deployment speed and efficiency. Before using this solution, our deployments took four to five hours. Now, we can deploy applications in ten minutes. The Ultimate version offers enhanced features for security scanning through DAST and SAST analysis, which have greatly benefitted our project workflow.
The licensing model could be improved to be more accommodating in terms of user numbers and costs. This would serve more users better.
I have been working with GitLab for three years.
We use a partner, and they are very competent. We have not had the need to open a support ticket directly with GitLab.
Neutral
We have saved time significantly, reducing deployment time from four hours to five minutes per deployment.
The price is high, and it limits user accessibility. When we shifted from the open-source to the Ultimate version, we had to reduce the number of users due to the licensing model.
We did not evaluate other options as we are currently satisfied with GitLab.
I recommend GitLab for security features and rate it eight out of ten.
However, the licensing model could be more flexible to accommodate a broader user base. I especially recommend it for public companies and government-related entities.
I am using GitLab primarily as a code repository and for CI/CD tools and deployments.
The feature I appreciate the most about GitLab is its ease of use and compatibility, which allows for straightforward building and deployment processes.
Continuous integration with deployment is very powerful, which is a significant reason for migrating from TFS to GitLab. Its documentation is extensive, and YAML files are user-friendly, making the deployment process more or less straightforward.
There are missing search features, particularly when searching repositories or applying filters. Additionally, I have encountered issues with the deployment of CI/CD pipelines, especially dealing with variable environments.
Creating a YAML file with numerous variables can be challenging without a way to separate them by different environments. It would be beneficial to have a user-friendly interface for setting up these configurations, instead of just writing YAML files.
I have been working with GitLab for a little over a year as I transition from TFS.
The stability of GitLab is impressive. Everything, including runners, functions smoothly without any issues.
Technical support from GitLab has been satisfactory. I have had meetings where they taught me, explained things, and provided guidance for starting from scratch. Overall, my experience has been pretty good.
Neutral
I am transitioning from TFS to GitLab, mainly due to the powerful continuous integration capabilities of GitLab.
Currently, I have two developers partially dedicated to creating the CI/CDs, Firebend, and repositories.
Migrating to GitLab is bringing time-saving benefits, and everything is easier to automate. This transition is crucial for us.
The pricing of GitLab is reasonable, aligning with what I consider to be average compared to competitors.
I am migrating from TFS to GitLab.
I would appreciate some AI-driven helpers, similar to Visual Studio's Copilot, integrated into GitLab. This could enhance the user experience by providing assistance during configuration. I rate GitLab a nine out of ten points.
We are using GitLab for source code configuration and for CI/CD processes.
The CI/CD process is very efficient. We are utilizing the pipelines extensively and gaining significant benefits from GitLab.
We are not using the AI process yet, however, I would like to see AI support in GitLab. Maybe it already does. I am not sure how it supports AI processes.
We have been using GitLab for two years.
GitLab supports us very well.
We do not have any direct technical support from GitLab. We ask questions to our IT department, and they may seek external support if needed.
Neutral
The initial setup was handled by our IT department.
GitLab is a cost-saving tool and is particularly effective for coding processes.
I do not have any recommendations or suggestions. I rate GitLab a ten out of ten.