GitLab

Pros

I like how easy it was to set up and configure. Adding runners (servers that build your code) was intuitive, CI/CD works fine. When you switch from GutHub, you must get used to the naming convention, but this requires only a couple of minutes to get used to.Overall I highly recommend GitLab for anyone who wants to set up such a platform on-premise.

Cons

When you switch from other tools like GitHub you see features that are missing, mainly in CI/CD. You can't update a global variable from a job and must use workarounds. The pricing is a bit high, especially for the Ultimate plan.

Alternatives Considered

Reasons for Switching to GitLab

Pros

GitLab is a superb source code managemanet provide. It is free. We can install it in our privet server also. As well as we can use their server with a free account. We use git for version control. GitLab provides awesome support for version control. It is a very easy tool. Anyone can use it very easily If someone has no more knowledge about versioning but He can use GitLab very easy. We can maintain our Repositories/Branchers. User access level also there. Currently, We use GitLab. We maintain feature branches, dev branch, and master branch. Everyone does not allow to merge code to the dev branch. If someone add merge request to the dev branch, our one-person review code and merge. Then we use GitLab it is easy for us. GitLab provides superb dashboard it very easy to review code. It shows all code changes with file by file. Easy to compare. As well as we can compare two branches vary easy. It provides a clear, unique, user-friendly dashboard. GitLab also supports CI/CD process. It's superb we can recommend for anyone. If our commit has some conflict it shows how to resolve that step by step.

Cons

When I add a new commit. If the file is large/have many lines. It not showing code changes directly. It shows a message file has many lines cannot show changes that kind of message. Sometimes when we compare two commits. It not more clear. Some times confusing. If I show some file history only show commits. not showing code changes by commits. We want to go and check every commits to show changes.

Alternatives Considered

Reasons for Switching to GitLab

Pros

User friendly interface, easy to use controls. The Visual Studio Code UI for inline editing of files is very helpful in case we want to update code directly in the web-UI without needing to download the code in local, edit in IDE and then push back it to the source control.

Cons

The latest update had moved the profile and sidebar to the left and has not given proper customization options to the user. The old interface of having it customizable was better.

Pros

The built-in CI/CD, issue tracking, and merge request features make my development process seamless and efficient.

Cons

The user interface can be overwhelming at first, and the learning curve is a bit steep for beginners.

Pros

It’s good for managing the development assets in IT. Easier to understand the conflicts for new starters also.

Cons

It’s good to have a user interface to understand any conflicts, issues etc., while using