GitLab Ultimate

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.

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.

GitLab  needs to improve the CI/CD functionality because it is not compatible with Jenkins  and other tools, as it is not that efficient. Security-wise, we have security features enabled in GitLab  for code vulnerability and other aspects, but it is not up to market standards.

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.

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.

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.