For any project, it's critical to know how the software is used, but tracking usage data is inherently difficult in open-source projects.
Anonymous usage statistics address this need.
When enabled, Jenkins periodically sends information to the Jenkins project.
The Jenkins project uses this information to set development priorities.
</div>
<h1>General usage statistics</h1>
<div>
<p>Jenkins reports the following general usage statistics:</p>
<ul>
<li>Your Jenkins version</li>
<li>For your master and each agent, the OS type and number of executors</li>
<li>Installed plugins and their versions</li>
<li>Number of items (like jobs) of each item type</li>
</ul>
<p>
This <b>does not</b> report any personally identifiable information. The only information reported by Jenkins is information inherently revealed by the HTTP protocol, such as the IP address.
These usage statistics are aggregated, updated monthly, and published to <a href="https://stats.jenkins.io">stats.jenkins.io</a>
</p>
</div>
<h1>Telemetry collection</h1>
<div>
<p>
In addition to the general usage statistics listed above, the Jenkins project collects telemetry data from specific trials to inform future development.
Each trial has a specific purpose and a defined end date, after which collection stops, independent of the installed versions of Jenkins or plugins.
Once a trial is complete, the trial results may be aggregated and shared with the developer community.
</p>
<p>
The following trials are currently set up on this instance:
For many security fixes, the Jenkins security team adds hidden options, sometimes called <em>escape hatches</em>, to disable the security fix.
This hedges against severe regressions not caught in testing, or unexpected legitimate use cases.
It is unknown to the team which of these options are actually in use, so this trial collects anonymous information about the values of (typically boolean) security-related Java system properties.