Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Bugzilla on the plugin site for more information.

The current version of this plugin may not be safe to use. Please review the following warnings before use:

This plugin integrates Bugzilla into Jenkins. It hyperlinks bug numbers that appear in changeset descriptions to the bugzilla bug detail page. It can also, optionally, add a tooltip to each linked bug, showing the bug 'summary' text.

This plugin needs a new maintainer

Jenkins needs to know the URL to your bugzilla server. In addition, you can specify a username and password to the bugzilla server. If login is required to see bug detail, then the username and password are necessary for the tooltip feature. Note that the password is stored in plaintext within Jenkin's configuration files. Here is an example configuration page, with the bugzilla project's own bugzilla server:

Once the plugin is configured, all numbers are hyperlinked and get tooltips. Since there is no convention to distinguish bugzilla bug numbers, all integers get hyperlinked. Here is a nonsensical example of a changeset on Jenkin's SVN server, linked with the mandriva Bugzilla database, with the mouse cursor over bug 1659. Note that the revisions are hyperlinked in addition to Issue 1659:

Change Log

Version 1.5 (Nov 05, 2011)
Version 1.4 (Jan 30, 2010)
  • Update code for more recent Hudson
Version 1.3 (Jan 29, 2009)


  1. Unknown User (dmulter)

    I enter the base URL for my system without the trailing slash, but always get the following error in my log when using the latest 1.2 plugin. The same URL works fine in the browser.

    WARNING: XmlRpcException starting bugzilla session: Failed to parse servers response: White spaces are required between publicId and systemId.

  2. Unknown User (eduardocerqueira)

    I am getting the same error described before, and I can't replace the current path "http://bugzilla" as example by normal way, so I changed directly in global.jelly file in plugins\bugzilla\WEB-INF\classes\hudson\plugins\bugzilla\BugzillaProjectProperty

     What should I do to have this working as expected without this error?


    Eduardo Cerqueira

  3. Unknown User (dmulter)

    The answer was easy, turns out my Bugzilla install didn't have XMLRPC configured. You need to install the optional module using:
    $ perl -MCPAN -e 'install "SOAP::Lite"'
    $ ./checksetup.pl

  4. Unknown User (doug.borg@integware.com)

    Using a regex with a look-behind solves that nasty problem where it will hyperlink ALL decimal numbers quite nicely.



    The above regex matches ONLY the numbers in strings like the following:

    Bug #12345
    Issue: 12345
    SCR 12345
    Bug 12345
    bug 12345
    bug #12345
    scr 12345
    scr 123456

    The regex does NOT match just any number. The number must be preceded by something like "bug", "issue" or "SCR".

    While there is no convention for what a bugzilla bug should be called, the regex above takes care of most of the ones we use at our shop. I am sure you could get even fancier with it, but this seems to work for now. I suggest something like the above be the default instead of matching all decimal numbers as the current default regex does.

    1. Unknown User (malfunction84)

      Using lookbehind is a brilliant idea to avoid linking all decimal numbers. Starting with Douglas's regex, I've created the following:

      (?<=[Bb]ug [\d, ]{0,64})(\d+)

      It will match and link multiple bug IDs. Examples:

      • Bug 12
      • Bug 12,30
      • Bug 12 30 54
      • Bug 12, 30, 54, 81

      Due to the limitations of lookbehind, you can't use + or * in the lookbehind, which is why I've resorted to the curly braces. I welcome any improvements.

  5. Unknown User (cfox)

    I'm trying to set this up to work with a SSL required Bugzilla, but get this complaint from the plugin, "Error contacting bugzilla XMLRPC at this URL" and no traffic is shown by tcpdump on the remote server. If I change the https:// to http:// then tcpdump shows traffic, but of course the plugin fails. Is there something special I need to do or is SSL unsupported? I see the sample shown uses SSL (https://qa.mandriva.com//show_bug.cgi?id=1659) so seems like it should be supported.

    1. Unknown User (malfunction84)

      I had the same issue, and I resolved it by ensuring that the certification path for my SSL cert was trusted.  I ended up having to add an intermediate CA cert (for Godaddy) to Java's cacerts file.

  6. Unknown User (a.d.chowdhury@gmail.com)


    Will it be possible to configure multiple bugzilla location in the system and in projects appropriate one is chosen. Like Ant of JDK...


    Aniruddha Dutta Chowdhury

  7. Unknown User (das)


    We are users of Fogbugz and a small change in the plugin will enable its use: instead of using a fixed string to access the case (now /show_bug.cgi?id=) set this string as a parameter of the plugin. In particular default.asp?. This will expand to: http://myfogbugz/default.asp?CASE_NUMBER instead of http://myfogbugz/default.asp?/show_bug.cgi?id=7449 (when I set the base URL to http://myfogbugz/default.asp?)



    1. Unknown User (tmz030180)

      Hi David -

      Are you using the bugzilla plugin for fogbugz?  If not is there a fogbugz plugin?



  8. Unknown User (skazi)

    Hi! Is it possible to use this plugin to update Bugzilla e.g if I want to populate the 'Build Fixed' field in Bugzilla for a given bug, with the build number from Jenkins when the build is successful and if it's list of changes includes that bug?

    Or is there some other pluginto do that?