Plugin Information
| Plugin ID |
mantis |
| Latest Release |
0.8.3 |
| Latest Release Date |
Jul 26, 2009 |
| Changes in Latest Release |
via Fisheye |
| Maintainer(s) |
n/a (java.net id: sogabe) |
| Issue Tracking |
Open Issues |
Mantis Plugin
This plugin integrates Mantis Bug Tracker to Hudson. Mantis is a free popular web-based bugtracking system written in PHP scripting language.
This plugin decorates Hudson "Changes" HTML to create links to your Mantis issues, and update issues with private / public notes.
As an example, if you committed a change with the following log message (which is configurable see Project Configuration):
Mantis keys in changelogs are now hyperlinked to the corresponding Mantis issue pages (complete with tooltips), 
and Mantis issues are also updated with note as following.

 | This plugin only supports Mantis 1.1.0 and above.
1.2.X is experimental. |
Configuration
System Configuration
First, you need to go to Hudson's system config screen to tell Hudson where's your Mantis.
- URL - the root URL of your Mantis installation, eg. http://example.org/mantis/
- Version - version of your Mantis installation. 1.1.X or 1.2.X(1.2.0a3 and later, this is experimental)
- User Name, Password - user name and password of your Mantis installation to update relevant Mantis issues.

Project Configuration
In the top section, select the url of your Mantis installation.

- %ID% is placeholder which means Mantis issue id.
In the Post-build Actions section, choose "Updated relevant Mantis issues" (option).

 | To Update Mantis issues, Mantis user must have at least "DEVELOPER". |
 | This plugin updates Mantis issues if build is stable or unstable. |
Trouble Shooting
If you have ran into trouble,
- Select New Log Recorder in System log screen.

- Configure Log Recorder. Logger is "hudson.plugins.mantis", log level is "finest". and save.

- Update Mantis issue...
- See System log. Check SOAP request and response.
Changelog
Version 0.8.2
- check if user has Job.CONFIGURE, not ADMINISTER when configuring project (issue 4077).
- fixed NPE in M2 project (issue 4049).
- replaced deprecated classes and methods.
Version 0.8.1
- Support subversion plugin.
- Saved regexp pattern per build, which enables link in old history even if configuration is changed.
Version 0.8.0
Version 0.7.1
- Support Mercurial changelog, which requires Mercurial Plugin 1.15.
- Support Git changelog, which requires Git Plugin 0.5.
- Fixed a bit.
Version 0.7
- Record changelog in Mantis note.
Version 0.6.1
- Don't change build status if failing to add note. (issue 3005).
- check permission.
Version 0.6
- Hudson 1.281 and later required.
- Supported Mantis 1.2.0a3 and later (experimental) (issue 2877).
- Logged SOAP Request and Response.
- Improved error diagnostics.
Version 0.5.2
- Use default issue id pattern if project configuration has not saved after upgrading(issue 2307).
Version 0.5.1
- Improved performance of hyperlink to mantis.
Version 0.5
- Configurable Mantis issue IDs patterns (issue 2117).
- Hyperlink to mantis even if checkbox is not checked (issue 2117).
Version 0.4.3
- Fixed UnknownFormatConversionException (issue 2116).
- Improved Japanese translation.
Version 0.4.2
- Added more logging for debugging.
- The username and password of Mantis installation is now optional.
Version 0.4.1
Version 0.4
- Update mantis issue if build status is unstable.
- Support unsigned server certs.
Version 0.3.1
Version 0.3
- Support HTTP Basic Authentication(Not Mantis's BASIC_AUTH)
- Fix small bug
Version 0.2
- Remove mantisconnect-client-api.jar.
Version 0.1
Comments (5)
May 08, 2008
Tom Larrow says:
Thank you very much, this plugin works great!Thank you very much, this plugin works great!
Jun 12, 2008
Travis Bailey says:
I like to throw the ability to use HTTPS on the heap of features. Our Mant...I like to throw the ability to use HTTPS on the heap of features. Our Mantis install is remote from our Hudson install and don't like any passwords going unsecure.
Additionally, is it reasonable to make this plugin update mantis even when unstable a setting or something? I mean we run unstable right now a lot because we have a few broken tests out of 500+, I hate the idea of losing mantis updates just because someone has a test in a broken state.
Jun 28, 2008
Seiji Sogabe says:
please use the issue tracker for RFEs and bugs.please use the issue tracker for RFEs and bugs.
Sep 01, 2008
djcarr says:
Apologies for mentioning it here, but I'm not sure if its a bug yet. My b...Apologies for mentioning it here, but I'm not sure if its a bug yet.
My build works and creates artifacts:
(from System log)
2/09/2008 15:22:41 hudson.model.Run run
INFO: Wombat Compile #54 main build action completed: SUCCESS
This will succeed if there are no Mantis references detected.
but if there are Mantis references detected, the bit at the end that creates the Mantis notes fails, and so the whole build fails.
(from console)
[MANTIS] Failed to add note to Mantis issue #4,564 (cause: Access Denied).
[MANTIS] Failed to add note to Mantis issue #14,665 (cause: Access Denied).
[MANTIS] Failed to add note to Mantis issue #14,748 (cause: Access Denied).
finished: FAILURE
My Mantis setup:
Mantis 1.1.1
$g_login_method = MD5;
Mantis user "hudson" with global "reporter" access to all projects
My Hudson setup:
Hudson 1.232, mantis plugin 0.43 & 0.5
Mantis URL, username "hudson" and password set
HTTP Basic Authentication fields are blank (as we don't use it on our intranet)
I have tested manually by logging into Mantis as "hudson" and can add notes to the above issue numbers.
Any idea what I might be missing? What kind of setup is the plugin being developed against? Is there any other config or log file I can check?
Thank you!
Sep 02, 2008
Seiji Sogabe says:
Mantis user "hudson" with global "reporter" access to all projects The Mantis S...The Mantis SOAP API that the plugin uses requires "DEVELOPER" access level to add note.
See api/mc_config_defaults_inc.php 16L,
If you replace "DEVELOPER" with "REPORTER", It will work..