GitLab Premium Self-Managed

I maintain my code and run CI/CD pipelines on my code when I commit and push.

The fact that you can structure your code and do version control on your code.

The fact that you can set up a CI/CD pipeline is a great thing that they added. It has been there already for years, but that is the one I use the most and play with the most.

The continuous integration pipeline allows you to automatically test and stress test your applications. You can test and make sure the code that you write is secure.

Because if you host it on your own premises, you can do the security yourself. I don't know about the online GitLab, but I use it privately, so it is hosted on my own servers.

Some more analysis on the code on default would be helpful.

The combination of AI and deterministic calculation based on the code would be an improvement.

I have been using it for four years or five. I used GitHub eight years ago already. The difference between GitHub and GitLab is overlapping, of course.

The stability rating is 99.

Scalability is quite okay. It is just adding an extra disk and it works.

Not really. It is mostly quicker to just do it yourself.

The initial setup was quite easy.

I think it is 30% better than using a public GitHub because then you are not sure your data can be cracked in your code.

I am working with a paid version of GitLab [Private Offer Only], but that was related to what tools I use. It is okay.

GitHub is hosted on the servers of Microsoft and GitLab [Private Offer Only] can be hosted on your own premises. That is, in my opinion, the biggest point of sale that was used to buy GitLab [Private Offer Only] instead of GitHub.

I could use AWS myself, so I could do that, but we don't do that. My overall rating for this product is 7 out of 10.

My basic use case for Gitlab was the ticket management, the wiki, the CI/CD pipeline, and the code repository. These four use cases form my core usage.

Gitlab is a developer tool, and it was easy to use. I never had to go to Jira or any project or product management tool. The wiki was there, so the onboarding of my developer was super fast.

Having everything in a single place in GitLab means I do not have to go to any other tool while I am working on GitLab. That was the major advantage. The ticket management was the part that I was using in GitLab. Since I was a solo developer, I never used Integrated Code Review in GitLab extensively. However, for teams, it is really useful. Integrated Code Review is definitely an important feature in GitLab because as soon as the code is committed in a branch, the deployment is a major aspect. Making sure that the build is working fine, testing it, and having it deployed is critical, and GitLab provides a good feature in that area. I have not heavily used the security scanning part of GitLab. The ticket management and wiki part I mentioned earlier was what I was using with one of my team members in GitLab.

Since GitLab [Private Offer Only] the main part is the Git part. With AI being available, I see one thing happening. For example, Claude Code allows people to connect Jira or ClickUp, and then they connect GitHub to get the work done. If you can bring in a feature of the AI that can help do the project management and the code commits in a single MCP since the project management is in GitLab [Private Offer Only] and the code is in GitLab [Private Offer Only], that would help get rid of Jira and all these things. This will have two benefits. One, the onboarding will be easy. The second thing is people will not have to pay an additional amount for Jira or ClickUp.

I was using GitLab for my personal project for the last five years, not for professional projects.

I never had any issue with GitLab. For me, it is stable.

For me, GitLab was a scalable solution.

I never had any problem and never had to reach out to the support of GitLab.

I have used the cloud version of GitLab. I have not tried the self-hosted version, so I cannot comment on that. I never got a requirement to have a self-deployed GitLab instance.

Developer time is important. If you save time in the development with GitLab, that is a value of money. If things are getting done faster, then that is a good ROI. It varies team by team, but based on my experience, GitLab saved my time between 10% to 15%.

I was using the free version of GitLab , but I think the price is comparative and not a major differentiator.

When I started using GitLab, I wanted a combo of the features. There was ticket management, there was the wiki, and there was a CI/CD pipeline, everything was there. GitLab was the first to provide all these things, and later on, GitHub has taken all these things, but GitHub is a follower. GitLab is the pioneer of these things. That is why I started taking it and that was the main motivating factor for me.

GitLab is on its own cloud. It is AWS, and I used Kaspersky for my servers when I was doing PCI DSS for one of my companies. I rate GitLab an eight out of ten.

My main use case for GitLab is as a version control system that we are using. Currently, I am working on an end-to-end AI pipeline, and I have deployed my whole code using GitLab so that all things are utilized for version control for my back-end AI and front-end team. We merge all the Git codes into GitLab, and my CI/CD, issue tracking, security, and monitoring is maintained inside GitLab.

We try to collaborate with all the teams together on different features. Within GitLab, we are not utilizing Jenkins or any product management tools because it perfectly renders all the information. It maintains the version control system, which is very helpful to containerize and deploy all services, allowing us to have everything together in production.

CI/CD is the most important feature that I am utilizing with version control and security as well, and all things are very useful inside GitLab.

CI/CD helps my workflow by allowing me to integrate any new changes or any new version that I want to deploy in the whole ML lifecycle, which I implement through new integration phases and identify updates in the deployment scripts. We generate YAML manifest files, add dependencies, and deploy them utilizing GitLab's versioning system, identifying any security patches that need to be added or incidents that need to be managed, triggering the workflow. We try to manage the perfect scenarios.

GitLab has impacted my organization positively in terms of version control systems, providing many smart features and reducing the sharing of dependencies compared to what we used to do previously. It has helped the organization merge and collaborate within the team on the level of code accesses and identify how actionable insights can be inputted within the whole pipelining mechanisms, allowing us to easily perform actions on CI/CD. My organization has adapted this and resulted in more productive work.

There are many improvements that GitLab can implement, such as addressing the issue of caching. Currently, when I have multiple tasks to merge or attempt multiple merges, the CI/CD and overall GitLab processes get slower. Implementing caching to allow parallel jobs to execute together would optimize the solution and enhance efficiency.

The UI is not user-friendly compared to how GitHub Actions operates. If we could customize the UI interface or have options for plugin-based mechanisms, that would be more suitable and increase DevOps in enterprises.

I have been using GitLab for around three years.

GitLab is stable.

GitLab's scalability is good, allowing multiple employees to work together, change code collectively, and perform all kinds of CI/CD regardless of impacts from bug fixes.

I have not reached out to customer support currently, but email support is very good, although I have not interacted with any call-based mechanisms or voice call systems.

I was using GitHub and GitHub Actions prior to this. While GitHub Actions provided good CI/CD operations, GitLab has added smart features, such as a graphical view of branches in version control mechanisms and tracking changes made by authors at specified times. Everything is maintained perfectly in my codebase, and I can easily track buggy code, identifying issues with excellent visibility. This visibility compared to GitHub and GitHub Actions is what led me to switch to GitLab.

The setup cost for GitLab is minimal since the team has its own minimal resource balancing. The costing falls into an intermediate stage and is impactful across all results within the team. It allows for CI/CD stages and addition of security patches smoothly, with only a slight charge that is not significant. Everything related to scripting, processing, management, and deployment works fine.

I have seen a return on investment with increased collaboration within the team resulting in more productive work and a reduction in time based on prior experiences, which emphasizes GitLab's usefulness.

The setup cost for GitLab is minimal since the team has its own minimal resource balancing. The costing falls into an intermediate stage and is impactful across all results within the team. It allows for CI/CD stages and addition of security patches smoothly, with only a slight charge that is not significant. Everything related to scripting, processing, management, and deployment works fine.

Before choosing GitLab, I evaluated options like GitLens and Bitbucket. I have tried those tools prior to this project, but ultimately, I chose GitLab as the foremost solution for version control mechanisms.

Since using GitLab, we have experienced fewer errors in identification, and any incidents coming out at the production level can be maintained to facilitate complete results, ensuring that collaboration works fine and deployment scripts remain easily executable, maintaining all services perfectly. Any impactful scripts work fine, whether making minor or major version updates.

I recommend GitLab if you are looking for a good graph-based solution or any impeccable solution for version mechanisms. I would rate this product a 9 out of 10.

My main use case for GitLab is utilizing it in three main ways: one is using the Issues and Epics tracking for tasks, the second way is using the Wiki, which is the documentation feature, and then the third way is for code management.

Out of those three, I find myself using the Issues and Epics tracking feature the most often. I really quite like it because I find it clear and clean to use, and it works well when using it with numerous people.

We use the Issues feature to record our tasks and assign those out, as well as recording the description of what the task requires. Then we use the Epics feature to group the issues into categories, which makes it easier to track the tasks at a higher level.

In my opinion, the best features GitLab offers are the Issues and Epics feature, which I find very clean and clear to use, and it is very quick and responsive. I also quite value the Wiki feature because both of those are built into the same platform, making it very easy to bounce between the two and create links between the boards and the Wiki.

The ability to link between the boards and the Wiki helps my workflow and collaboration with my team by ensuring that if we have any tasks that need to be carried out, we have them on the Issues board, and we write runbooks in the Wiki on how to carry out the task. We copy the link of the Wiki and put it into the description of the tickets so that when someone is working on the ticket, they can very quickly go over to the Wiki and know how to carry out their task, which saves us time.

GitLab has positively impacted our organization by making our code very secure because GitLab prides itself on security. Storing code in GitLab is a very secure way to do it, and from an operational efficiency and time-saving perspective, the Issues and Epics board is definitely helpful, offering a few benefits operationally.

The only feature I have used in GitLab that I thought could be improved is their code generation feature. When I previously used it, some of my questions were met with responses saying that it did not know the answer, and some responses were incorrect as well. I understand this is something new for them, so they are still developing it, but I do not feel that it is in a position where I would use it regularly just because it is not very reliable right now.

I have been working in my current field between five to ten years.

GitLab is very stable. I have not seen any instability issues.

GitLab is highly scalable and could very easily scale to thousands of code repos, which is necessary for any organizational size.

The customer support for GitLab is very good, and I have no complaints because they have always been quite helpful. I would rate the customer support a ten out of ten because I have never had any issues with them before, and they are very knowledgeable.

Personally, I have previously used GitHub and Bitbucket as well. I find that GitLab has the cleanest and clearest UI out of all of them, and it has numerous features, such as the Issues and Epics tracking feature, as well as the Wiki feature, which sets it apart.

I have seen a return on investment. Any company that generates its own code and develops applications needs a code base, so it is more of a necessity rather than choosing something because it results in a measurable benefit. However, in terms of operational efficiency, a ten to twenty percent increase in speed could quite easily be seen from using the Issues and Epics tracking feature.

Regarding pricing, setup cost, and licensing, to my understanding, GitLab offers competitive rates. There are a few big competitors within this space, such as GitHub and Bitbucket, so GitLab prices themselves competitively.

Before choosing GitLab, I did evaluate other options, and the main competitors I considered were GitHub and Bitbucket. They are great as well, and all three are brilliant, but GitLab, in my opinion, has the cleanest UI, which sets it apart.

I would recommend others to use GitLab because it is a great tool and there are not any real major drawbacks, just a minor one related to the AI code generation. I have given this review an overall rating of nine out of ten.

GitLab is a major help for DevOps automation, primarily for version controlling and deployment purposes. I use GitLab for DevOps automation and version control in my daily work by creating many branches for each environment through which deployments can be controlled and version control can be maintained. When we need to make a change only for the dev environment, we simply make the code change for the dev branch, and only the servers connected to the dev branch receive those changes applied while the rest remains the same. In a similar way, we can particularly target a group of servers, which prevents other issues from occurring. GitLab helps tremendously in this purpose.

GitLab has role-based access control, so when a team member needs to make a code change, they cannot directly apply it to the environment but must put in a merge request. Once a senior reviews the code and approves it, then it is implemented across the environment, making it safer and allowing everyone to experience the process.

The best features GitLab offers are version control and automation, which are the major things that stand out to me. When it comes to access, the login is very smooth, with just one login integrated with our Okta, allowing everyone to log in easily. Deployments become much easier, and that is how GitLab helps.

The automation features make my work easier because we use a tool called AWX, which is connected to GitLab. Whenever we run a job on AWX, it directly checks the code and uses it. Since the code is not preserved locally but kept in the cloud, it is safe and nobody can tamper with it. When it comes to safety, that is a major thing. Automation features allow the code to be accessed from any tools we use, so the jobs we run are helping tremendously and doing their work perfectly.

For pipeline tasks, we have created a significant amount of pipelines, which are all hosted in GitLab. Running the pipelines has become much easier, and they are doing a perfect job, helping tremendously in our day-to-day activities.

GitLab has positively impacted my organization because previously we stored code locally on servers, leading to many risks. Since GitLab came into our environment, our integration and deployments became much easier, helping our work become much smoother.

Improvements from GitLab have led to better team collaboration because when several people are working, they can all edit the code and submit it as a merge request, and once approved, it reflects directly to the main branch. Many can work at the same time. When it comes to deployments, deploying has become much faster since we started using GitLab, and even if errors occur, we can spot them easily and troubleshoot, which has helped tremendously.

I believe GitLab can be improved by making integration with other platforms a little easier. I understand it is a matter of security, but it would be much more helpful if it could integrate with other tools more seamlessly.

When it comes to speed, if multiple users are committing their codes, it takes a bit longer, which I think can be improved. Fine-tuning resources might help, but apart from that, I have not felt many improvements, as everything is going smoothly.

I have been using GitLab for the last five years.

GitLab has been very scalable in my experience. Even as our count of servers and applications grows, we can still support our needs with GitLab, which is why I find it very scalable.

I have had experiences with GitLab's customer support, and they have been very supportive. I have not faced any issues from their side till today.

I have not used a different solution before GitLab. From the day I started working in my organization, I have been using GitLab. While I heard they were storing all the codes locally on servers previously, I have not experienced that.

Before choosing GitLab, my organization evaluated other options such as Jira and Atlassian, but the major advantage of GitLab led us to choose it.

I would rate GitLab a 10 on a scale of one to ten because it is perfect in all ways. I choose 10 because the offerings provided by GitLab are very useful in aspects like deployment, team collaboration, and deployment speed, all of which GitLab helps with tremendously.

If you are looking for faster deployment, team collaboration, version control, and better use of CI/CD pipelines, my advice is that GitLab is the best option for you, so go and try it out. I give GitLab an overall rating of 10.