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

Using Git as a configuration management tool is already common sense (essential), but I think this software is the most used for remote (distributed) development. There are many cases where you install Git on each person's terminal and operate the commands, but if it is team development and you can't use an "external (public Internet) repository", it is better to set up and operate a Git repository with GitLab I think it will be the safest and standard way to use Git.

Cons

I guess there is no choice but to get used to it, but I would like to see more visual changes and expressions (messages) when conflicts occur that are easier to understand for beginners. After all, I'd like to see them develop an interface that makes it easier to understand the concept of Git configuration in the first place.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

Integration of Code repository with pipelines which run on the fly in its own container with minimum effort to deploy.

Cons

Too many features at times make it difficult to look or search or navigate to

Pros

An alternative to github that we can run on our own hardware and control our own data.

Cons

Upgrades can be difficult as the automated portions fail at each major upgrade and require manual intervention.

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

It essentially operates the same as github, however, it scales much better. I really enjoy gitlab, even though in some instances it isn’t free. Good choice for your next project.

Cons

I don’t love that’s it’s not free. It’s kind of a deal breaker for some, especially because github exists.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

The UI is really straightforward, set-up a in-house deployment also is super easy , and cheaper

Cons

Sometimes apply the updates is a bit tricky

Pros

Straightforward alternative to the Github experience. Good layout. Does not get in the way. Tracks what needs tracking.

Cons

Purely that it's a different experience from Github, which takes some getting used to.

Pros

Like that it's very complete and easy to use.

Cons

CICD Pipelines are sometimes a bit difficult to develop.

Alternatives Considered

Reasons for Switching to GitLab

Pros

It's open source, they are improving a lot and there are a ton of features for everyone.

Cons

sometimes the UX is just behind GitHub.
Some performance improvement could be great alghough it may depends on our own server.

Pros

It's opensource though provides a cloud based solution with a really good free tier. It allows integrating code repositories with issue tracking and continuos integration and continuos deployment

Cons

User experience could be largely improved. Searching and filters are a bit clunky from the UX point of view. Also bulk actions are only allowed at project level.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

Gitlab gives us sufficient features to support source code management, user administration and Continuous integration for reasonable pricing

Cons

There is really nothing in my mind which I specifically do not like about the GitLab but If there would be room for improvement, We would appreciate more features for CI/CD integration testing.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

I like Gitlab in most ways. It has great task management that integrates well with code changes. As a Git server, it does everything you need. It's relatively easy to administrate. If you stick with the well-supported features then Gitlab will serve you well.

Cons

The technology is showing its age and can be frustrating to use. Integrating custom runners can be shockingly painful. I have run into UI bugs that allow tasks to be run before their dependencies are met which has caused serious release problems. Designing pipelines without a system like Github actions is incredibly fiddly and error prone.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Pros

Gitlab has features to set up project wiki, deployment, CI/CD pipeline and managing the project with role management with adequate space for personal projects.

Cons

The documentations are bit confusing and third party plug in integration is bit difficult and confusing.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

GitLabprovides a complete end-to-end solution for software development, from source code management and version control to deployment and monitoring. This can be very convenient for teams who want to consolidate their development workflow in a single platform.

Cons

One potential limitation is the complexity of the platform. While GitLab's comprehensive feature set can be a strength, it can also make the platform more challenging to use and configure, especially for smaller teams or organizations.

Pros

Gitlab is simply the best version control and project management tool for any organisation, period! It has everything you need in a greatly priced package. It is my go to tool for my personal projects as well as used in every organisation I have worked with. I even tried to host their community version myself which was great. The documentation is well laid out, breaking changes are communicated well. Apart from this, the CI/CD functionality is easy to use, UI easy to navigate, reporting/labelling/tagging features are one of the easiest.

The free plan for individuals or small team covers everything you need.

Cons

None I can think of. I even like the new UI introduced recently.

Alternatives Considered

Reasons for Switching to GitLab

Pros

1. Free of cost
2. Highly efficient, does the job without uncertainty.
3. Never observed any downtime
4. Very frequent and proper updates to the software.
5. easy to maintain
6. can easily integrate with jenkins for Continuous Integration- Continuous Deployment.
7. Easy to setup and use, no support or setup or external teams required. Anybody with minimum computer skills can get this up and running.
8. easy integration with youtrack for issue tracking and merge requesting tracking

Cons

These are not very big cons, but I find them annoying and could definitely use improvement:
1. The edit description on an open merge request also shows up on the history. So If somebody were to make a 10 different changes to the title while keeping the
2. The code formatting in the description box is not too good. It can take several tries before getting it right.
3. There is no way of searching for something based on a line of text. For example if you were looking for a commit or a merge request but you only remember the
4. sometimes very challenging to go back and undo merges which are quite complex.
5. on a given pr, it shows icons of all the participants but doesn't say which participant did what... for example if 5 people have just viewed a pr and done nothing else even then it shows all of them as participants. It would be nice to have a feature which will only show activity by participant on every pr.
6. text based Search via ui is practically no existent. So if you search for something using a text which is part of a commit message, chances are it will not show up 100%.

Pros

I started using GitLab for an external project and I like the following:
1) Easy to work with and auto explanatory. Creating/configuring a new repository is really easy.
2) Great CI/CD implementation. Having the repository with built-in CI/CD is really convenient, you can have everything related to the build and deployment process saved along with your code. I have used bamboo and I really appreciate this feature, it might have its problems but it is really useful.
3) Unlimited private docker registry, you can have your own private registry for free. I cannot express how useful this is.
4) In order to help with the CI/CD process it allows the creation of tokens with access restrictions (read only), so you can use these tokens to download your code or your docker containers without having to provide your personal credentials.
5) It has its own task manager
6) It has free agents that are in charge of executing your builds/deploys so you don't have to provide your own resources.

Cons

1) Configuring build variables is really messy and it is not an ideal implementation. I haven't found a way to set different values for them depending on the branch, so configuring different environments is not too easy
2) Even though having your code with CI/CD is really convenient, it has some drawbacks. If you have an established continuous deployment process that you repeat in many projects and you want to change it (maybe a fix it or improve it) you will have to add that change to all your repositories and all the branches that you want to deploy. So it is a really good feature but it is not too flexible
3) The task manager is messy, and I didn't find a way to have a shared board.
4) It does not have too many software integrations, as I mentioned before I have used bamboo and I really like their integration with other software

Pros

Project operation: Using GitLab provides the user with complete control over their projects. Users can easily follow up activities assigned to their respective partners. Additionally, the program gives you the advantage to have members across the borders as well, hence it is pretty useful and comes in handy when the work is beyond the borders.

Easy to use: GitLab is easy to lean and very easy to use the software as it helps in creating a project by giving instructions from the beginning. The tutorial mode is extremely helpful and because of that no experience or expertise is required to exhaust all the features offered by GitLab.

Cons

Contact Support: Although GitLab provides a good platform for its users, unfortunately, their contact section is poor. Users are unable to recover if they face any problem as the administration is limited. Administration can only be at your service if you own the premium version.

Complicated: Although Gitlab is easy to learn when it comes to the menu users tend to feel as if they are lost in some sort of maze. The menu is pretty much clunky because of this some of its users are unable to use GitLab to its full potential. Additionally, the efficiency of users is reduced to a great extent when they wish to search for aspects because it consumes time and energy.

Pros

The biggest pro for us at JeFawk Games (me and my freelancing friends, not employees as stated) was the fact that it allowed for 1GB of space for free in private repos! Since we're working on games, we really needed the space and the privacy. This was from before GitHub was acquired by Microsoft and gave away unlimited free repos.

Time forwarding a bit and GitHub is giving out free private repos of max 1GB with the option to use the Large File Storage thing, which in GitLab you don't need to bother with as you get it by default.

It includes DevOps and a lot of other features that frankly we don't make use of.

It's just the much bigger space by default and up to 3 collaborators. GitLab is great! Although it does have some cons....

Cons

One of the biggest problem with GitLab is that their website is a bit laggy. You can wait 1 to 4 seconds for some pages to load.
Another issue is that we actually use the GitHub Desktop application to handle GitLab repositories and the setup to connect the application to GitLab is kinda clunky, more like to allow GitLab to be grabbed as URL. Wouldn't wanna go through that again, hopefully they already streamlined it as last time I did it was about 2 years ago.

Pros

GitLab is an easy to use and versatile project management tool. As a team, we use it not only for software development projects, but also for the follow-up of our other projects. It is really great that it is customizable, you can simplify your interface for your teammates who cannot use complex applications. This offers you a more user-friendly product.

Cons

It's a little harder for people other than engineers to adapt. You shouldn't expect traditional drag-and-drop kanban boards. It's a bit of a technical product. But if we consider that the intended use of the product, this is really normal, not a big minus.

Alternatives Considered

Switched From

Pros

The source code can be managed anywhere as long as you are connected to the Internet. The editor also supports Once editing is finished, you can manage versions by connecting to the Internet and clicking, so you do not need to be connected to the Internet all the time. The source code editing software also supports this, so you can manage it with GUI button operation.

Cons

There is issue management, but there is no task management feature. Therefore, we are forced to handle GitLab + Redmine. If you have a task management feature, you can consolidate with this, and work efficiency will increase.

Pros

GitLab has all the must-have features for complete development and deployment flow.
The easy-to-configure pipeline is a differential, mainly due to the possibility of installing the agent (GitLab runner) in our infrastructure.
Issue management and merge requests are excellent and do not fall short of your direct competitors.
I use the GitLab in the cloud (SaaS) and on-premises, and it supplies my DevOps needs and team collaboration on the code review process.

Cons

On bitbucket, it is possible to see in realtime when a coworker is reviewing the merge request (pull request). It would be great to see this feature on GitLab too. The Runner registration is a bit harder when using an automation like Ansible.

Alternatives Considered

Switched From

Reasons for Switching to GitLab

Pros

I believe this is the best Github competitor which offers more configuration flexibility in setting up your development lifecycle.

Cons

The menus are not very UX friendly. There are lots of options when using Gitlab and sometimes is hard to find the particular section you need. It's annoying but having in mind all the good things that Gitlab offers, it's negligible.

Alternatives Considered

Switched From

Pros

Gitlab has been a great collaborative tool for us which allows for very customize-able build pipelines and easy issue tracking. The ability to add comments to code snippets and open up un-resolved threads allows you to stay on top of suggestions. Having to manually resolve those threads on your code comments before merge means that you are unlikely to accidentally push code forward without addressing those suggestions. There are also a good number of settings that allow you to control options such as how you want to handle merge commits, giving you complete control over your repository.

Cons

The main issue I have with GitLab is that the UI can be confusing and unclear. I am not a fan of the stacked diff view when comparing code changes. Compared to another version control system like BitBucket, I find it a bit more work to sort through the changes in a merge request. It's something you get used to, but initially is a bit unintuitive and less enjoyable.

Pros

GitLab stands out because it's an all-in-one platform for software development. It covers everything from storing code to testing, security, and teamwork. Developers in my team work together more easily and efficiently. GitLab also supports automation and follows best practices, making it great for speeding up development and ensuring good software quality. It's user-friendly, versatile, and works well for various types of projects.

Cons

One common drawback of GitLab is its relatively steeper learning curve, especially for new users or smaller teams. The platform's extensive feature set can be overwhelming, and the complexity of its interface may require some time to become proficient.

Alternatives Considered

Reasons for Switching to GitLab

Pros

The pipeline system is by far GitLabs most important feature, though the extensive offering of supporting services such as project wikis, hooks and integrations make it a flexible control center for all needs of software development.

Cons

Debugging pipelines seems to be less than an after though, with minimal support and no indication of being in anyone's focus. Monitoring seems like a lackluster proof of concept released to the public, with many issues being ignored for years and all around extremely poor support unless the only thing you want to do is monitor the default setup for the default metrics in the default view.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

The working style of most of the CI/CD tools are similar in the background. The ones that has better UI and fast responses are making a difference in the market. Gitlab CI, by far has the best UI. The button clicks, flows and placement of the features are very well-designed.

Cons

I cannot say least but I would be happier if Gitlab adds more UI features in CI/CD level.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

It is a great largest Git hosting service. Since the system can be deployed in the local on-premises environment, we are operating it experimentally. The CI function can also be evaluated as excellent. This is the best option if local demand exists. It is good not to have large amounts of components and libraries that confuse things.

Cons

When running a large project, the response is usually slow. However, I had no problems with it myself. I am satisfied.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

GitLab does its best to help you with what you may need in order to promote quality code deployments with tools and resources to become a more collaborative team. With source control and hosting repositories as its primary objective, GitLab extends to its users an extensive suite of tools and controls to ensure only quality code is committed and only by those that is desired. With features like code reviews, pipeline validations, and allowing for integration of automated tests, its hard to imagine low quality or bug infested code to get through to your production or master code branches.

Cons

Honestly, its not easy to pick out cons of such a great tool in your arsenal. Given that so much goes so well once you've integrated everything properly, the only things that come to mind are more of a annoyance rather than an issue and coincidentally, they're all based on the UI or aspects that don't interfere with the workflow or the work itself. One of which is that GitLab does not offer a dark mode of its UI. Given we are developers and spend most of our time looking at computer screen, It would be lovely to be able to darken the UI so that its not so straining to our eyes. Secondly, we have split up our GitLab in to various teams where each of the teams have access to their own folders/repository. Unfortunately, whenever someone from ANY of these sub-repos is given access, opens a new merge request, or is making comments on a merge request, everyone gets an email about it. It can be very frustrating and I'm not really sure if this setting can be changed from a User level but I would really love it if they can.

Pros

The most important feature is source code managing tool. App provides interface for GIT client. Creating a merge request is easy and you don't need to use console, it is possible to achieve this goal also on mobile! Another most important feature is CI/CD integration. Gitlab provides its solution to do this. You can define configuration and run tasks on GitLab runner, which can be easily installed on any server.

Cons

It provides a less functions than other software and a UI is a bit non modern.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

A huge number of features.
Intuitive and easy to use.
Extensive documentation and good customer service.
Flexibility of customization.

Cons

It can become expensive, particularly if the company has many users.
Some less-known external tools cannot be integrated.

Pros

Gitlab offers you a secure space to store and manage your git repositories, for personal use and or for your organization's development team. You can easily assign tasks to team members, and track and follow up on them with clearly laid out and categorized Kanban boards.

Cons

Gitlab's UI and UX are quite overwhelming for a first-time user. If you are new to Gitlab and you haven't used a similar platform like Github or Bitbucket before, you will definitely need a little training to fully utilize your Gitlab space. Make sure to get through the entire onboarding tutorial to avoid feeling lost because it's all going to seem very clunky and difficult to find your way at the beginning.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

GitLab does well as an all-in-one software development platform.

Cons

If GitLab makes a billing problem, it may refuse to rectify the problem as they did with us.

Pros

GitLab is easy to use and offers a versatile range of applications. GitLab can be used not only for software development projects. Especially in the academic sector, institutions can use GitLab to persist the respective work steps and research data, data in general, and workflows. Version control is particularly helpful in this regard, as it allows each step of a work to be traced, and errors to be undone directly without having to do a great deal of extra work.
In addition, GitLab can be customized and the respective instances can be easily transferred to one's own infrastructure. The development team is also always open to new ideas and actually incorporates them.

GitLab is therefore not only suitable for software development, but for any form of project in which it is a matter of the step-by-step tracking of work steps.

Cons

GitLab can be quite overwhelming. It is particularly difficult for non-experts from the non-software sector to get to know the processes of GitLab, as GitLab is less focused on gamification aspects compared to GitHub. Therefore, a high level of preparatory work and expertise is required in GitLab. Likewise, GitLab is often very technical, which is understandable, but it would be quite conceivable that especially in the area of testing and CI, modular principles, like for websites, would be conceivable and desirable.

Alternatives Considered

Reasons for Switching to GitLab

Pros

GitLab is a great integrated SCM, Issue Management and CI/CD solution which is a pleasure to work with. The tools feel very nicely integrated and cooperate very well. It embodies by default the best practices for code management and is developed by a company which has open source and transparency at its heart, thus reassuring that the product can be trusted, either as a SaaS solution or as a self-hosted solution.

Cons

The SaaS version of the problem has over the year suffered some issues; however these have been decreasing over time and the company has made a hosted experience on par of those of other SaaS solutions. The resource consumption of the product is not to be taken lightly; however for small teams it has a relatively inexpensive monthly server cost.

Pros

I am not constrained at all by a company like GitHub or Bitbucket. It allows my team to have faith that what we are working on - remains in house. For piece of mind - without using git native.

Cons

Difficult to setup for the uninitiated linux administrator. Administration and upgrades are also difficult to do.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

GitLab is an awesome tool to use everyday. It is simple and easy to install on premise. The free tier is enough for any small business / team.

What really makes GitLab stands in front of the competition are its awesome CI/CD workflows. GitLab CI is incredible, you can do anything you want with it from building your sources, checking your code quality, deploying your projects... It is possible to make connections between various pipelines and have multiple repositories connected together to build your final "big" project.

Cons

Even if GitLab is simple to use, it's a big piece of software that can sometimes become slow on the web user interface.
Moreover the review system is sometimes not so easy to use compared to other competitors. Hopefully their are great browser extensions that solves this issues.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

This product is excellent and has both enterprise edition and community edition making it very inexpensive to get into and then moving to enterprise once setup and still very inexpensive compared to other options out there. You also can set up a private gitlab server either in docker or bare metal. I cannot rave enough about git lab.

Cons

There's not much to not like about it. It's a very capable system that can be deployed in every type of way imaginable. If I was to nitpick then I would say adding additional users can be a pain without having self registration available.

Alternatives Considered

Reasons for Switching to GitLab

Pros

You just forget about Gitlab. As it provide a whole devops toolkit, it integrates discretely in your workflow. It doesn't require training, and if needed for advanced use, it got an extensive documentation as any open source tool should have. The UI makes it easy to use without thinking about it. What you don't understand first, you'll find an usage if needed on day.

The fact it got integrated CI/CD is incredible. I am very reluctant to Docker technologies and wouldn't beat myself to deal with them, but I really like them the way they are integrated in the CI/CD: it makes possible to test the applications in a very efficient and simple maneer and improve the overall quality and security of my products.

Cons

What I really don't like is that, if it is possible do deactivate some feature of a repository because you don't use them, there are some that overload the UI and you cannot remove them because Gitlab use it as a way to make you upgrade to the next plan.

Pros

GitLab allows users to easily store their code projects and files in a safe and secure environment, allowing easy collaboration amongst users.
You can import repositories from other Git tools (such as GitHub) with ease, GitLab also imports any version history and accompanying branches.
The ability to make certain repositories private is excellent, most similar git systems charge extra for this service.

Cons

The user-interface, though clean and responsive, can be hard to use and master. Especially for new users, training is definitely required.
The integration with interfacing tools is lacking, most systems (such as GitKraken) require a premium license to connect with GitLab.
User management can be complicated, as the user interface isn't particularly clear here, and the different levels of access aren't clearly identified.

Pros

GitLab CI is great. The GitLab CI/CD language allows us to build complex pipelines easily, pipeline's configs are stored in the repository as well, so we can manage everything in one place. GitLab also has built-in Docker registry. We have both our build pipeline and our images hosted on GitLab.
The pricing is also flexible, I recommend it for both startup and large enterprises.

Cons

Explore Projects feature can be better, it would be more useful if we have a filter to select projects by technologies.
Should support templates on the job level, so it can be reused between multiple environments.
Lack of integration: there are not many 3rd party services that integrate with GitLab for now.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

Integration of CI/CD and Kubernetes for easily developing and running custom apps. Fantastic collaboration features like discussions, visual diffing. Some of this stuff you don't even get on desktop apps that charge big bucks. Frequent updates that inch its capability and usability forward. Good documentation. Wonderful community, welcoming atmosphere, pleasant to work with all the employees I've encountered.

Cons

Sometimes things break. When things are broken, sometimes it can take some time to be fixed, if you're not willing or able to fix it yourself. One of the consequences of such broad scope and feature development velocity. It would be advisable to keep another copy installed separately for testing updates before applying them to the live edition, if your IT has the capacity to do so.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

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

The products has plenty of features, as well as supporting all the basic Git operations/merge requests, you are given a wide choice of CI pipelines you can set up from within the project. Need more? Integrations with metrics, error tracking, kubernetes, snippets and more.
I never had any problem so far, it's stable and always up.

Cons

The major issue for me is that these features are advanced, and if you want to use the repository as just that, you find yourself overwhelmed with loads of choices that you don't really need. Therefore, sometimes I find it hard to look for a button which should be the most visible element on the screen. Additionally, I found the arrangement of information in the "merge request" screen a bit counterintuitive compared with similar services.

Pros

- Excellent UI that is easy to understand: many of our developers are migrating for the first time from other software (github, bitbucket) and a constant comment is that the ui is intuitive and easy to understand compared to previous software. The transition is always smooth.
- Feature-full product: Gitlab offers a variety of features that I have found to be excellent and of high quality. The code-review process in gitlab is always smooth with the ability to resolve or re-open discussions, address specific comments or the whole of the discussion, the ability to suggest and even apply and commit code from the ui is also a huge plus. The IDE is decent and the file editor is also decent. The CI/CD integration with gitlab runners is smooth, the notification system is great. I get an email whenever a test fails. All from the gitlab ecosystem, i do not need to go to circleCi or some other provider for all of this, which allows the ui and experience to be consistent.

Cons

At this very moment there is no feature or issue that I have found to be detrimental to my experience.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab

Pros

GitLab CI is by far the most valuable feature of GitLab. Travis CI was the first one to offer a YAML-file based build system - but it's GitLab CI to make pipelines very flexible and expressive. While Travis was okay for most popular languages in open source projects. GitLab made it possible to run enterprise-grade pipelines with many stages, each having multiple simultaneous jobs. This, plus git repository, Docker registry, and several other tools, making it a complete solution - starting from an early development cycle, through build, to deployment and monitoring thereof.

Cons

Several pages perform bad, e.g. pipelines list in big projects. Some pages don't have search and sorting. These are minor issues though.

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Pros

I use the GitLab Community Edition (CE) and the first thing I love about it is it's Open Source! I am a believer of Open source software! In my company, we host our own instance of GitLab CE and it's been smooth. We use it for source code hosting and for CI/CD. Source code hosting has been great. CI/CD is nice too. GitLab has all the features required by a code hosting software - groups, groups within groups, repos, role based access control for members. Members can also be grouped with names - helpful to create a group for a team and add members to the group and give access to the team/group. It has forking, SSH/HTTPS git repo access, Notification/Watch repo features. It also has lots of integrations. We use slack a lot and we have integrations with slack which GitLab provides, and we have configured it to get notified for different things, starting from commit pushes to pipeline failures. We also use the GitLab pages for hosting the Wiki site for repos. It's pretty neat! The GitLab CI/CD has the concept of runners which run the CI/CD tasks/jobs. Runners have tags, and you can easily use the appropriate tag in the config to run the task in the appropriate runner. We use different runners for different things like, pushing to a Docker registry (requires special permissions), accessing a prod DB/application, running normal tasks (scripts) etc. All in all, it's quite good

Cons

Although GitLab has lots of features. I do have some complaints about it. I hope that newer versions will make my complaints obsolete! Starting with the CI/CD, it's quite good. But it lacks some features and flexibility which we expect in the upcoming versions. Features like one CI/CD pipeline triggering another pipeline (not present in CE, not sure about Enterprise Edition) and things like grouping jobs in a stage. Also, the CI/CD UI is not very good. It has glitches, there's no auto refresh in all the UIs to show the status of a job - if it's successful or if it failed. The job UI also isn't very great, like, if the job names or stage names are big, it becomes tough to read. Also, when the job log is very big, it reloads the page when the job finishes and truncates the output of the job and makes it available for download instead. This can be good or bad, based on the use case. For us, it was mostly not a soothing experience.

Pros

GitLab has been a great resource for me as a developer, providing a user-friendly interface and lots of documentation for assistance. I can collaborate with colleagues, keep track of code changes, set up repositories and branches easily, and track issues, bugs, and feature requests, all of which help me stay on top of my projects.

Cons

Although GitLab is a great platform with many powerful features, it can be difficult to use and understand for those without much experience with version control systems. The UI can be confusing, and the language can be overwhelming. Additionally, there have been reports of bugs and other issues which can be disheartening. Ultimately, GitLab may not be the best choice for everyone.

Pros

GitLab provides all-in-one capability for developers to do Source Code Management, CI/CD automation, Security and coding standards checks. Earlier we used to have separate tools for each of the above functions, but moving to Gitlab we now have a single stop-shop for all our Application Development and Automation needs. I see many other companies are trying to follow the gitlab methodology but gitlab is way ahead of the competetion.

Cons

Project and Portfolio management can still have improvements to provide Roadmap and Grantt views in future versions

Alternatives Considered

Reasons for Choosing GitLab

Switched From

Reasons for Switching to GitLab