Dev Ops Engineer at a tech vendor with 10,001+ employees
Real User
Top 10
Jan 5, 2026
We are working with Black Duck, but we do have some plans to move to another vendor down the line. Black Duck is used mostly for security checks. For coverage, we are using a tool called SonarQube. Black Duck is explicitly used for security checks on code, for example, open-source software. We perform scans with Black Duck Security Checker, but software developers handle the post-remediations and mitigation of risks and vulnerabilities. For CI/CD, we are using GitLab Premium for our repositories. We have Artifactory for all artifact storage from JFrog Artifactory. We have Black Duck for security checks, SonarQube for coverage and unit testing, and Ansible for configuration management along with other tools. These tools are used for our CI/CD pipelines, running all our pipelines and having unit test cases executed with SonarQube and Black Duck for security checks.
Co Founder and Technical Architect at Think NYX Technologies LLP
Real User
Top 5
Dec 2, 2025
My use case for GitLab Premium involves consolidating multiple tools for different use cases such as performance testing, SAST, DAST, project management, and advanced project management. Initially, the organization was using close to eight or nine different tools. When I joined this organization as a consultant, they were already using the intermediate level of GitLab within the ecosystem. I recommended that rather than using multiple tools while already paying for them, they add some additional budget and move to GitLab Premium. This would help reduce the maintenance and management of multiple tools and eventually reduce the overall licensing cost.
DevOps Engineer at ENTERPRISE SYSTEM SOLUTIONS LIMITED
Real User
Top 5
Nov 6, 2025
GitLab Premium is being used, but the CI/CD functionality is not utilized. GitLab also provides the entire CI/CD ecosystem, but that is not being used. GitLab Premium is used for version controlling only. The primary use case for GitLab Premium is version controlling. Version controlling and triggering capabilities are available, and GitLab configuration is good, but not comparable to GitHub. GitLab Premium is used for internal needs only. GitHub Actions are used for enterprise clients, as GitHub is widely used across the enterprise client base. Maximum enterprise clients are using GitHub, while some clients are using Azure Repos. For internal purposes, GitLab Premium is used because most proof of concept work has been done with Jenkins, and automation testing is also performed with Jenkins. A dedicated server for GitLab Premium is maintained because there are more than 350 users. If GitHub were implemented instead, it would be costlier. GitLab Premium is less costly, which is the main reason for the choice. GitHub is used widely for enterprise clients, while GitLab Premium is used as a customer and user solution.
GitLab Premium provides enhanced features for CI/CD automation, security management, and version control, favoring a user-friendly interface and integration options suitable for efficient project management.GitLab Premium is designed for developers looking for robust CI/CD automation, secure management, and efficient version control. Users benefit from its seamless Docker integration, comprehensive project management tools like roadmaps, and the option for on-premises hosting that centralizes...
We are working with Black Duck, but we do have some plans to move to another vendor down the line. Black Duck is used mostly for security checks. For coverage, we are using a tool called SonarQube. Black Duck is explicitly used for security checks on code, for example, open-source software. We perform scans with Black Duck Security Checker, but software developers handle the post-remediations and mitigation of risks and vulnerabilities. For CI/CD, we are using GitLab Premium for our repositories. We have Artifactory for all artifact storage from JFrog Artifactory. We have Black Duck for security checks, SonarQube for coverage and unit testing, and Ansible for configuration management along with other tools. These tools are used for our CI/CD pipelines, running all our pipelines and having unit test cases executed with SonarQube and Black Duck for security checks.
My use case for GitLab Premium involves consolidating multiple tools for different use cases such as performance testing, SAST, DAST, project management, and advanced project management. Initially, the organization was using close to eight or nine different tools. When I joined this organization as a consultant, they were already using the intermediate level of GitLab within the ecosystem. I recommended that rather than using multiple tools while already paying for them, they add some additional budget and move to GitLab Premium. This would help reduce the maintenance and management of multiple tools and eventually reduce the overall licensing cost.
GitLab Premium is being used, but the CI/CD functionality is not utilized. GitLab also provides the entire CI/CD ecosystem, but that is not being used. GitLab Premium is used for version controlling only. The primary use case for GitLab Premium is version controlling. Version controlling and triggering capabilities are available, and GitLab configuration is good, but not comparable to GitHub. GitLab Premium is used for internal needs only. GitHub Actions are used for enterprise clients, as GitHub is widely used across the enterprise client base. Maximum enterprise clients are using GitHub, while some clients are using Azure Repos. For internal purposes, GitLab Premium is used because most proof of concept work has been done with Jenkins, and automation testing is also performed with Jenkins. A dedicated server for GitLab Premium is maintained because there are more than 350 users. If GitHub were implemented instead, it would be costlier. GitLab Premium is less costly, which is the main reason for the choice. GitHub is used widely for enterprise clients, while GitLab Premium is used as a customer and user solution.