GitLab vs. OpenText Business Process Monitor

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.

Incentivized

It is really good to have Business Process Monitor for being proactive with monitoring critical business services. And it is even more recommended along with APM. However, you will still need some training in order to configure them as they are sophisticated tools.

Incentivized

• 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.

Incentivized

• Being proactive in monitoring critical business services.
• Uses pre-saved scripts using Vugen.
• Almost all protocols are supported by it.

Incentivized

• 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.

Incentivized

• It depends heavily on Vugen so it would be great to give more courses on writing scripts in the Business Process Monitor trainings.
• When issues arise, we don't have insights into if the issue is from the script itself or if it is a real issue. Here you lose trust in determining which is right until you interfere personally. As an example, one day I got an alert from a business server and the issue was that the script didn't finish successfully and thus it kept the session opened. So the next schedule of the script will fail, not because there is a real issue on the business service, but because you need to go yourself open the application, close all pages, then log out so that the script will continue to monitor.

Incentivized

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.

Incentivized

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!

Incentivized

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

Incentivized

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

Incentivized

We didn't try anything else as we are satisfied with Business Process Monitor.

Incentivized

• 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.

Incentivized

• Proactive.
• Monitors critical services by simulating every step you could use and get alerts for performance issues and availability issues.
• Has almost all the needed protocols to write a script.

Incentivized