Mantis Source Integration
Released under the MIT license
The Source plugin provides a flexible framework for fully integrating any sort of Version Control System (VCS) with Mantis, including support for multiple repositories, changesets or revisions, and file path tracking. It has many features already, such as importing repository history and optional support for remote check-ins or imports, and utilizes a class-based API to access objects in the database.
- SourceBitBucket: Git repositories hosted on BitBucket.
- SourceCgit: Git repositories accessible via a cgit web frontend installation.
- SourceGithub: Git repositories hosted on GitHub.
- SourceGitlab: Git repositories hosted on GitLab.
- SourceGitweb: Git repositories accessible via a GitWeb web frontend installation.
- SourceHgWeb: Mercurial repositories accessible via a HgWeb frontend installation.
- SourceSFSVN: SVN repositories hosted on SourceForge.
- SourceSVN: SVN repositories locally accessible by the SVN binaries.
- SourceViewVC: SVN repositories accessible via a ViewVC web frontend installation.
- SourceWebSVN: SVN repositories accessible via a WebSVN web frontend installation.
Support for more source control tools should be rather straightforward to implement due to the flexibility inherent in the integration framework and API.
The Source Integration framework requires Mantis version 1.2.0 or higher.
The SourceGithub plugin requires Mantis 1.2.16. This is due to a new requirement in GitHub API v3 (User Agent header is mandatory for all API requests) enforced as of 2013-04-24.
Download or clone a copy of the Source Integration source code.
Copy the primary Source plugin (the
Source/directory) into your Mantis installation's
Copy all the remaining plugins, or just the appropriate ones for your repositories, into your Mantis installation's
While logged into your Mantis installation as an administrator, go to 'Manage' -> "Manage Plugins".
In the "Available Plugins" list, you'll find the "Source Control Integration" and additional plugins:
a. First, click the "Install" link for the "Source Control Integration" plugin.
b. Next, click the "Install" link next to any additional Source Control plugins appropriate for your repositories.
Click on the "Source Control Integration" plugin to configure it.
NOTE: an API Key must be set up to import changesets via shell. To generate a random key, run
openssl rand -hex 12
Go to "Repositories" and enter your repository name, select the repository type, and click "Create Repository" to begin adding your first repository.
Configure the repository, following the specific documentation for the relevant plugin extension:
Once configured, click the "Return to Repository" link and click either the "Import Everything" or "Import Newest Data" button to perform initial import of repository changesets and verify configuration.
Once satisfied that your repository is configured & working correctly, you can automate the import of new changesets by configuring a cron job on the web server where your Mantis installation resides, as follows:
import via curl (could run into timeouts on large repositories, or block your webserver)
import via shell
php-cgi -f plugin.php page=Source/import id=all api_key=<YOUR_API_KEY>
Please be aware of the difference between
php-cli. The import won't run with php-cli.
This will import new changesets for all configured repositories.
Add additional repositories as needed.
Problems or questions dealing with use and installation should be directed to the MantisBT IRC channel #mantisbt on freenode:
Bug reports or fixes are highly encouraged, and should be directed to the bug tracker on GitHub:
The latest source code can be found on GitHub:
Original project and documentation can be found on noswap.com:
- MantisBT 1.3.x - master-1.3.x branch
- MantisBT 1.2.x - master branch