GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts. GitLab helps teams across the complete DevSecOps lifecycle, from developing, securing, and deploying software. Differentiators, as described by Gitlab:
Simplicity: With GitLab, DevSecOps can…
$0
per month per user
OpenText SiteScope
Score 8.0 out of 10
N/A
OpenText's SiteScope is an agentless application performance monitoring tool with hybrid support across a variety of systems and vendors. Sitescope also offers automated workflow and incident identification and remediation capabilities, and rapid installation-to-monitoring processes.
As mentioned earlier, the features like chart visualization sets it apart from the others. Other than that, GitLab is open source while other are not and comparatively more secure that its other counterparts. Also, GitLab supports adding other types of attachments which is not …
When i was using the other platform, Some time i face down time, But GitLabs its not happening for single time. GitLab is having easy user interference as compared to other platforms. Pull Request, Code review, Issue tracking, Merging, Access control and User Roles is having a …
GitLab is miles ahead of the competition. In so many words, having a simple UI with robust security and the ability to conduct Git actions takes the cake. The competitions like to say they can do these things easily but their products are more confusing and hard to use.
GitLab allows a self-hosted version that is easy to setup and configure. It is also open-source as compared to GitHub. The integrated CI/CD tools is a plus, since we do not have to worry about those tools, unlike Github. The All-in-one solution of GitLab made sense for our …
Gitlab offers the best support for CI/CD pipelines and the highest degree of customisation for workflows, permissions, and integrations. The integration of BitBucket with JIRA is better than GitLab but CI/CD features are limited in comparison. GitLab's built-in Container …
Gitlab provides basic functionality like any other git tool. Some features of push and pull requests , clone and merge is handled equally well. It lacks in AI features which are there in GitHub and setup processes are difficult. Cost difference is the only concern while …
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution.
GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" …
It's much simpler than the competitors. The one important feature Gitlab stand out is the CI/CD pipeline. GitHub required integration with external CI tools but Gitlab has this feature built-in. Compare to Jenkins and Teamcity, It's easy to use without any additional Plugins. …
Gitlab seems more cutting-edge than GitHub; however, its AI tools are not yet as mature as those of CoPilot. It feels like the next-generation product, so as we selected a tool for our startup, we decided to invest in the disruptor in the space. While there are fewer …
i have more exoerence in GitLab rather than bitbucket . As personally , it is good for me to understand how things is going on. i have used personally and also in organisation . It is great for developer to see there 3 months ago code and also can come up with new solution to …
Because with Visual Studio code, it was very easy for us to install GitLab in it and have easy access through the terminal and due to GitLab, it was easy to implement codes regarding API and AWS services to make our software better. Gitlens and all features help to check the …
GitLab provides a far superior platform due to it's great integration and CI/CD focus. And while in the beginning the UI might look a bit overwhelming with use you will find it way more useful than it's competitors. The variables and settings also make way more sense and it's …
My feedback may not be important here because when I joined the company they already had GitLab and we still use it due to the ability to do CI/CD Integration, deployments, debugging, code owners approval, and Jira integration. So far we have not had any major blocker that has …
Github is more open-source first and enterprise-first second in their approach. The reverse is true for GitLab. Both are exceptional products and it highly depends on the specific needs of an org
GitLab has a open-source community and great documentation that provides support resources and community contributions. AWS CodeCommit is used for integration with other AWS services in the AWS ecosystem and also have a low community and support compared to GitLab hence …
It was a management decision to use GitLab over other tools. It integrates well with RBAC using Terraform. Runners are easy to setup. Almost all the features the organization used before are available in GitLab.
For small projects or companies that do work on a few only code repositories selecting one of the git code hosting services like GitLab, GitHub, Bitbicket etc does not make a big difference.
But, if you are on a code development company that handles too many repositories and …
Software delivery is the key objective and GitLab made it much easier to hit the group quickly. It worked well with automation, and integrations with other SDLC tools used in the Organization and it is really easy to use. It's widely adopted and has the power to deliver what we …
GitLab's online IDE and code modification is much better compared to Stash. While pricier than Bitbucket, Gitlab also provides CI CD configuration better than BB.
SiteScope unified console is a powerful tool for operators to easily detect warnings and alerts grouped by its hierarchical organization with real-time status displaying continuously the whole health map.
The product offers unique out of the box monitoring templates and offers the flexibility to create our own conditions for alert generation in case of an event. It integrates well with the other Micro Focus suite applications, hence all alerts from various tools can be viewed …
Like I've mentioned before, SiteScope is a basic overall monitoring tool used primarily for the helpdesk here at my company. We do not use it from a detail perspective in the networking area. SolarWinds is primarily for that since it is more detail oriented. Uptime is really …
Nagios can also do most of the things that HP sitescope can do, but HP sitescope is right on target when it comes to infrastructure monitoring and also cost effective which is why we selected HP sitescope. We also have teh iPhone and Android apps which are very useful for …
As far as the interface goes Solarwinds is much prettier and intuitive but it is also a very busy interface which makes navigation difficult at times. Also setting up alerting under Solarwinds requires you access the desktop of the machine running the application whereas …
I will begin by saying that I "inherited" SiteScope". So, it really was not my choice as to whether or not I was going to use it. Also, we were so heavily ingrained in SiteScope, that it would have taken a HUGE overhaul of our monitoring system to switch to something else.
It is well-suited for any project that needs VCS. It's an excellent choice for teams that might be remote or have to collaborate across teams. Plenty of features allow for async working. With its dashboards and reporting features, it is also suitable for nontechnical PMs or stakeholders. It allows for very bespoke customization and can most often do much more than you need it to.
It can be used to monitor the uptime and availability of the URLs in the production and non production environments and detailed reports of the URL availability can be extracted to check, monitor the performance of the URL in variety of regions from where it is accessed. It requires specific knowledge of integration with the other Micro Focus tools for alerts generation and routing to correct focal points, so needs to improve a little on the UI part of the tool as it is a licensed tool and needs to ace the game for many free tools are also available in the market, which can do the job.
Custom monitors with custom thresholds, timing, polling, and many other configuration options.
Custom ways to alert and notify. Of course you have email and text message capabilities, but SiteScope also allows for specific messages and variables within those messages to be sent out so that your alert is data filled and you can know exactly what is going on and why you received that specific alert.
Monitor templates for quick and rapid deployment of one's standard set of monitors. Easy ability to "copy" and "paste" monitors so there is no need to re-create from scratch.
Scripting. SiteScope also allows for custom scripts to be called from specific alerting triggers. This allows for HUGE and POWERFUL customization and automation through SiteScope. You can easily have scripts that "take action" on a specific alert so you don't have to!!
Very easy to use in my opinion. Learning curve is very short and you can master this system fairly quickly for all of the depth of customization that it offers.
I really feel the platform has matured quite faster than others, and it is always at the top of its game compared to the different vendors like GitHub, Azure pipelines, CircleCI, Travis, Jenkins. Since it provides, agents, CI/CD, repository hosting, Secrets management, user management, and Single Sign on; among other features
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!
I've never had experienced outages from GItlab itself, but regarding the code I have deployed to Gitlab, the history helps a lot to trace the cause of the issue or performing a rollback to go back to a working version
GItlab reponsiveness is amazing, has never left me IDLE. I've never had issues even with complex projects. I have not experienced any issues when integrating it with agents for example or SSO
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
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution. GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" in GitLab while you have to do clickops in GitHub to achieve the same. No overview of code in branches is a minus when we tried to figure out what our colleagues are trying to merge as it looked off.
I will begin by saying that I "inherited" SiteScope". So, it really was not my choice as to whether or not I was going to use it. Also, we were so heavily ingrained in SiteScope, that it would have taken a HUGE overhaul of our monitoring system to switch to something else. SiteScope does not have a discovery option. Not like others you may have sampled (i.e. SolarWinds). The plus is that you monitor exactly what you want with no plethora of other junk you may not want. The "negative" is that you must set up all the monitors. I know I did mention the templates and copy/paste features, although it can be streamlined, it is still a manual process for each server. SiteScope is all a very manual process while others crawl your network and discover stuff.