First, identify the location of the issue.
Are you reporting an issue in Jenkins itself or one of its plugins?
We document all the issues in Jenkins on JIRA and plugin issues are on Github.
If you are reporting an issue with the jenkins.io site, please create an issue in our GitHub issue tracker.
After that, determine what kind of issue it is. There are three main types:
whose use is explained on this page:
Bug: Something does not work as intended.
Improvement: Either a current functionality should be improved or new
functionality should be added.
Vulnerabilities: Security related issues in Jenkins
Other types (Patch, Task) are not used in JIRA.
Neither will be explained here.
If you want to propose a patch, create an issue using one of the 3 types above, and then create a pull request on GitHub as explained here.
Report issues with infrastructure services hosted by the Jenkins project (jenkins.io, accounts.jenkins.io, etc.) at the dedicated help desk.
Before reporting a bug
First, search for the error message or general problem description.
This can help you find solutions if it’s actually e.g. a configuration
problem, or point you to earlier reports in case you’re not the first
one experiencing this problem. You can
use the search
in the issue tracker, or use web search.
Stack Overflow may also be a
good place to search. Any results will often point you to earlier issue
reports if it’s really a bug. You can then watch them and vote for
Stack Overflow may also be a
good place to search.
Any results will often point you to earlier issue reports if it’s really a bug.
You can then _watch them and vote for them in JIRA, or subscribe to notifications in Github Issues.
Voting helps us determine the impact of bugs and prioritize them.
If you have doubts that the problem you’re experiencing is the exact same one as you found, and prefer to file a new issue, be sure to mention the one(s) you found in the description.
issue (and mention the one(s) you found in the description)._
Make sure that the problem actually is with Jenkins. If your build
seems to fail for no reason, try to build your project outside Jenkins,
but in the same general environment (e.g. same machine, same user
account, …). If Jenkins interacts with other systems, make sure that
they’re working. If the connections between Jenkins controller and agents
fail, make sure the network is reliable.
Check the changelogs to see whether the issue has been fixed in
newer versions of the affected component.
For Jenkins itself, review the long term support changelog, the LTS upgrade guide, and the weekly changelog.
If you believe the problem to be in a plugin, review the changelog for the specific plugin on the plugins site. The plugin documentation can also be reached
directly by clicking the plugin name in Manage Jenkins » Plugins » Installed.
If you’re still unable to resolve the problem and cannot find existing
issue reports or related fixes in newer versions of Jenkins or the
If you’re still unable to resolve the problem, and cannot find existing issue reports or related fixes in newer versions of Jenkins or the plugins, file a bug.
Before requesting an improvement or feature
Check newer versions of Jenkins or the plugin for this feature.
They may have the feature already!
Search JIRA or Github Issues for existing requests for this feature.
You can then watch and vote for them.
Voting helps us determine the demand for requests and prioritize them, so it’s in your interest to actually find these rather than creating a duplicate.
If you cannot find anything, file an improvement or new feature request in the issue tracker for the specific plugin.
Open the page for the plugin and select the "Report an issue" link in the Links section on the right side of the plugin page.
Searching for existing issues makes it easier
for us to deal with issue reports and shows which
issues are considered important by the community by the number of voters
and watchers. It increases the likelihood of related changes.
It’s not that obvious when an issue has been reported separately several
times with only a few watchers each.