Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsIn the CNCF’s 2024 survey, Jenkins was selected by 44% of respondents and GitLab by 43% as a tool they currently use to manage CI/CD pipelines. Those figures describe a multiple-choice survey of people already using or testing CI/CD tools—not market share or usage across all software organizations.
What the CNCF survey says about GitLab and Jenkins
The CNCF 2024 Annual Survey, published by the Cloud Native Computing Foundation and Linux Foundation in 2025, asked respondents which tools they currently use to manage CI/CD pipelines. Among 596 valid responses to that question, Jenkins was selected by 44% and GitLab by 43%.
As an Amazon Associate I earn from qualifying purchases.
The question allowed respondents to select more than one tool. The percentages therefore show how often each option was selected within this survey group; they do not divide a fixed market into exclusive shares. The one-percentage-point difference does not establish that Jenkins is meaningfully ahead of GitLab in the broader software industry.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Other tools in the same survey
The same question recorded GitHub Actions at 51% and Argo at 45%. These figures provide context for the Jenkins and GitLab responses, but they remain selections from the same defined respondent group—not global usage rates.
#1 Best Overall
Who the figures represent—and who they do not
The tool-use question covered respondents who said they were using or testing CI/CD tools. Its 596 valid cases are a survey sample, not a census of software organizations. The results are useful as a snapshot of those respondents’ reported tool use, but they cannot establish how many organizations worldwide use either platform.
Year-on-year results in a survey should also be read in their own sample and question context. A comparison across survey years does not mean the same individuals were tracked over time unless the source explicitly establishes that. The figures here do not justify claims that one platform is gaining or losing users relative to the other.
Why the GitLab report is a different kind of evidence
GitLab’s 2024 Global DevSecOps Report surveyed more than 5,000 DevSecOps professionals worldwide and reported that 64% wanted to consolidate their toolchain. That finding offers context for organizational interest in integrated workflows, but it is vendor-published survey evidence, not an independent market census.
Free tools Windows power users keep installed
One-click scans. No signup required.
Its population and question differ from the CNCF tool-use question. The 64% figure should not be combined with the CNCF percentages or treated as corroboration that a particular share of organizations uses GitLab or Jenkins.
What Jenkins project statistics can tell you
The Jenkins project’s 2024 in Review, published January 16, 2025, describes project activity and support and points readers to Jenkins project statistics. Those measures can help explain the state of the Jenkins project, but they are not automatically comparable to a survey asking respondents which CI/CD tools they currently use. Before interpreting any project metric as adoption, check its definition, denominator, and collection method.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to use the numbers when choosing a CI/CD platform
Adoption frequency can indicate that a tool is familiar within a particular survey population. It cannot determine whether that tool fits a specific team. Consider the requirements the surveys do not measure directly:
- Repository-hosting context: Consider where your code is hosted and which integrations your existing workflow needs.
- Toolchain approach: Decide whether you want a more consolidated workflow or are comfortable operating a separate CI system alongside other tools.
- Operational and security requirements: Identify the controls, maintenance responsibilities, and pipeline capabilities your organization requires.
The cited figures do not establish comparative cost, performance, security superiority, or migration effort for GitLab and Jenkins. Those questions require evidence specific to your team’s setup and requirements.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
