Likelihood to Recommend We started to use GitLab for hosting git source code repositories of our projects only but slowly we started to use it to store container images, packages, dependency proxy as well infrastucture registry and it is now well suited for Continuous Integration in our projects, It wasn't that good in Continuous Deployment before 12.0 version but after 12.0 it is amazingly good for Continuous Deployment as well since it keeps deployment information in a well organized manner which can be configure in ci yaml configuration.
Read full review More appropriate for:
Pure Microsoft ecosystem environments (Windows Server and SQL server) and the most common Linux and UNIX platforms. Environments where cost is less of a factor than settling on a single platform for monitoring Environments where the administrators are familiar with the setup and installation of SCOM. Less appropriate for:
Pure UNIX/Linux shops, especially versions not supported out of the box by SCOM. Shops that cannot afford the engagement to setup/configure and maintain on a continuous basis. Shops that cannot dedicate personnel to the care and feeding of SCOM, especially when supporting larger environments. Read full review Pros GitLab excels in managing code versions, allowing easy tracking of changes, branch management, and merging contributions. It helps maintain code stability and reliability, saving time and effort in the development or research workflow. Powerful code review features, enabling collaboration and feedback among team members. Robust project management features, including issue tracking, kanban boards, and milestones. Read full review Allows us to visualize our systems in a single interface and see the status of health as well as relevant performance metrics. A flexible and powerful interface with active alerting covering domain controllers, SQL servers, etc... Allows you to customize your views and workspaces for specific tasks and needs. Reporting is powerful and flexible. Read full review Cons CI variables management is sometimes hard to use, for example, with File type variables. The scope of each variable is also hard to guess. Access Token: there are too many types (Personal, Project, global..), and it is hard to identify the scope and where it comes from once created. Runners: auto-scaled runners are for the moment hard to put in place, and monitoring is not easy. Read full review One of the biggest drawbacks to SCOM is the sheer scope and complexity of the system. This can be a pro and a con. The system is very customizable, what you put into it is what you'll get out of it. That said, the learning curve is fairly steep. An organization needs to be committed to putting time and resources into SCOM to get the most out of it. I've heard stories from colleagues of several different companies that invested in SCOM and then abandoned it due to the excessive time and care required. SCOM is expensive. Not only is the enterprise licensing costly, SCOM requires it's own servers, operational and warehouse databases to be maintained. The OOB SCOM reports are a bit clunky and feel outdated. Read full review Likelihood to Renew Gitlab is the best in its segment. They have a free version, they have open-source software, they provide a good service with their SaaS product, they are a fully-remote company since the beginning (which means they are fully distributed and have forward-thinking IMO). I would certainly recommend them to everyone.
Read full review Usability I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!
Read full review Support Rating At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when
GitHub was acquired by Microsoft
Read full review Hard to get support. The product is not being actively developed anymore, so it is hard to get new features for the product.
Read full review Alternatives Considered GitLab is easily the preferred tool when it comes to versioning and source control. With other tools the UI often feels outdated and clunky leading to inefficiency and confusion. With some of the sleeker tools such as
GitKraken , while the aesthetic is pleasing, the experience is plagued by a lack of support, lack of optional plugins, and a plethora of bugs that cause unnecessary legwork to resolve. GitLab is the best of both aesthetic and functionality
Read full review We used Altiris and WSUS and in the beginning Altiris had the better admin interface than SCOM, but it is no longer the case as SCOM has refined their admin interface. Altiris still has better and more robust group assignments for management roles and those two other tools can better manage non Windows OS devices than SCOM but for a large enterprise Windows shop, if you can afford it, SCOM is the way to go.
Read full review Return on Investment We were able to streamline our project's codebase which made us very organised and laid out a proper plan for development. Our deployment and infra pipelines are well structured now making our process 10x faster. We are more focused into project building rather infra, as infra is totally on autopilot mode. Which has enabled us to grow our ROI by records. Read full review It has allowed us to provide an Enterprise Event/Alert management solution to the Global company It has taken a long time to get it to provide valuable alerts and information, lots of user resources and investment. It assists with 24/7 monitoring and out of hours support Read full review ScreenShots