$t_svnlog_xml = shell_exec( "$svn log -v -r $t_rev:HEAD --limit 200 $t_url --xml" );

Not sure why but after that line in SourceSVN.php is run, $t_svnlog_xml is missing the last </log> tag and the call to process_svn_log_xml() fails. I hacked around it with $t_svnlog_xml.='</log>'. When I run the SVN command manually, the trailing tag is there. Weird.

When i want to install the Source plugin i have this message

APPLICATION ERROR #2503

La mise à jour du schéma pour le plugiciel a échoué en bloc #2.

My mantisbt version is 1.2.12. please help

While trying to get the MantisBT service hook on Github working together with my mantisbt installation (including source-integration), I think I recognized that the submitted data of the service hook has changed.

Right now the following data is submitted during the hook:
https://github.com/downloads/01-Scripts/source-integration/payload_data_array.txt

I'm attaching some code-changes that solved the problem for me.
Maybe someone can check the changes.

APPLICATION ERROR #401

Database query failed. Error received from database was #1292: Incorrect datetime value: '2012-12-04T11:11:04Z' for column 'timestamp' at row 1 for the query: INSERT INTO mantis_plugin_Source_changeset_table ( repo_id, revision, parent, branch, user_id,
timestamp, author, message, info, ported, author_email, committer, committer_email, committer_id
) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ).

Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.

HgWeb integration plugin still requires Meta, despite b536bb7 and information at http://comments.gmane.org/gmane.comp.bug-tracking.mantis.general/3434

BTW, does it work?

My team and me are using github, so we create a organization to manage our code.When I use SourceGithub to import our private repo to mantis, it failed.
Only return
Retrieving master ... failed (Not Found).

I create application both on my account and my organizaion, the auth passed, but i can't import, why it's failed?

Hello,

Windows 7 Prof SP1(32) - All Updates/Fixes applied (Locale: de-DE)
IIS 7.5
PHP 5.4.9
MantisBT 1.2.14 (Locale: Default)
SI-Plugins (VCS 0.18, SVN 0.16, WebSVN 0.17)
WebSVN 2.3.3
SQLServer Express 2012
Subversion 1.7.8
TortoiseSVN 1.7.11

1. Source Integration only works if I set the MantisBT.SQLServer.LogonAccount(User).Language to 'English', due to Locale issues with 'Matis_plugin_Source_changeset_Table.timestamp'. DateTime will not work reliable on Values with 'yyyy-mm-dd hh:mm:ss' format like '2013-03-07 12:00:00 (3rd of July 2013 on my system), or '2013-03-17 12:00:00' (out of range exception - 17 is not a month in my Locale) on SQLServer. Given format depends on Locale on all versions of SQLServer.

Possible Resolutions:
a) Advice to set the language of the MantisBT User on SQLServer to 'English'. Easy done, only one.
b) Use ISO 8601 Format 'yyyy-mm-ddThh:mm:ss' on Updates/Inserts.

I don't care, but please adjust the format of dates in changelogs. I get someting like '2013-03-20T15:52:57Z'. Would prefer '2013-03-20 15:52:57'.

2. For lang.DE:
   change $s_plugin_SourceWebSVN_websvn_path = 'WebSVN Path...
   to $s_plugin_SourceWebSVN_websvn_path = 'WebSVN Pfad...

Martin

I noticed a small bug on Source plug-in config page. If the checkbox « Bug Fixed Assign To Committer » is not check, this setting is not saved in database.

Change 'Matis_plugin_Source_changeset_Table.timestamp' type to (Unix)timestamp.
Rationale:
a) All other dates in MantisBT are implemented this way.
b) Any server-side interpretation of dates is avoided. At least on MSSQLServer all 'Y-m-d H:i:s' dates depend on
Locale.

Follow-up(issue #53)

LG M.

My configuration is MantisBT 1.2.12 with SQL Server 2008

An error occurs when opening repositories management page :
operand text is not valid for count operator

the query is

SELECT COUNT(DISTINCT filename) FROM mantis_plugin_Source_file_table AS f
JOIN mantis_plugin_Source_changeset_table AS c
ON c.id=f.change_id
WHERE c.repo_id=?

My workaround is to use VARCHAR column type instead of TEXT

ALTER TABLE mantis_plugin_Source_file_table
ALTER COLUMN filename VARCHAR(250) NOT NULL

Maybe VARCHAR(MAX) would be better ?

Based on my testing, this is a regression caused by the fix for #34 (commit a419068).

Hey!

According to this documentation,
https://noswap.com/projects/source-integration

Private organizations with github are not supported. But this was written 3 years ago. Are they supported yet? Is there any reason why I might be having a problem? What would be required to make this work?

When fixing an issue, the URLs on the email body are http://localhost/... instead of using the actual server hostname.
When adding notes or updating issues, emails are sent with the correct URL.

e.g: (sorry, but it is on PT-Br)
Issue fixed by SourceSVN:

O seguinte caso foi RESOLVIDO. 
======================================================================
http://localhost/mantis/view.php?id=107
====================================================================== 
Relatado por:               reporter
Atribuído a:                developer

Issue updated:

O seguinte caso foi ATUALIZADO. 
======================================================================
http://hostname.of.my.server/mantis/view.php?id=107
====================================================================== 
Relatado por:               reporter
Atribuído a:                developer

When fixing bugs, a not is added in public state, and this is hard coded.

I just hard coded it to private for my needs, but it would be nice to have this either use the default for adding bug notes, or eventually have it configurable through a new variable.

On a windows installation SVN might require a custom argument to work properly.

In specific "--config-dir C:\Users\Administrator\AppData\Roaming\Subversion\config"

The function check_svn() in SourceSVN.php doesn't take the arguments in account - and hence SVN-integration is failing on line 265 without any logging of explanation.

Currently I work around this issue by commenting line 265. But more ideal would be a NON-generic error, the console output and to include the svn arguments.

Using the Source & SourceGithub plugins from master, I get the following error when running an "Import Latest Data" on a repository which fails:

APPLICATION WARNING #300: String "plugin_Source_import_latest_failed" not found.

I have confirmed that the plugin_Source_import_latest_failed string does not exist in master.

When the plugin picks up a commit by a user registered in the tracker, it resolves the issue and assigns it to that user, even if they are not developers.

Example http://www.mantisbt.org/bugs/view.php?id=16871

Hi,
I've installed the plugins on my Mantis and tried to integrate with GitHub.
But I get the following error when importing data on a repository.

APPLICATION ERROR #401
Database query failed. Error received from database was #1048: Column 'revision' cannot be null for the query: INSERT INTO mantis_plugin_Source_changeset_table ( repo_id, revision, parent, branch, user_id,
timestamp, author, message, info, ported, author_email, committer, committer_email, committer_id
) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ).

Any help will be appreciated.

Thanks

Hey guys,

I'm not sure I understand what parameters to set in Update Repository view on Mantis.

What exactly should I specify in GitHub Application Client ID ?
Should I create new OAuth app in https://github.com/settings/applications ?
If yes, what call back url I'm supposed to specify ?

Thanks.

Navigating to http://noswap.com/projects/source-integration works fine, but going to http://noswap.com/projects/source-integration/ (with a final slash) returns a 500 error.

On MantisBT 1.2.8 the installation of the SourceIntegration appears to fail. The plugin does not create the required database tables.

This leads to critical errors such as:
Database Query failed. The report message is #-1: ERROR: relation "mantis_plugin_source_bug_table" does not exist LINE 1: SELECT * FROM mantis_plugin_Source_bug_table WHERE bug_id IN... ^ for the query: SELECT * FROM mantis_plugin_Source_bug_table WHERE bug_id IN ( 6987,7094,7093,7092,7023,6319,7015,7021,7016,7033,7057,7078,7024,7036,6979,6284,7014,7025,7077,7063,6086,6479,7091,7009,7035,6967,6709,183,6800,7084,7086,7088,6992,7090,1299,6252,6124,7002,6719,7075,7087,6671,6952,7071,6416,690,7055,7085,6473,6584 ).

There is no reason or message given on why the database tables are not created.

#1048: Column 'author' cannot be null error occures when trying to import changesets with Gitweb.

Problem is in commit_changeset( ) where newline chars are stripped off of the input string, but the regexp is checking for a newline.

Proposed fix is to change the \n to \s* in
preg_match( '#author(?:<a[^>]>)?([^<>])(?:)? (?:<a[^>]>)?<([^<>])>(?:)?(?:<[^<>]>\s_)?\n\w, (\d_ \w* \d* \d_:\d_:\d*)#', $t_gitweb_data, $t_matches );

I am proposing \s* for better readability when checking the actual output of Gitweb.

Same problem happens with
preg_match( '#

Changing the \n to \s* fixes the problem

I was wondering why suddenly the GitHub integration does not work anymore.
The reason is that GitHub now requires a valid user agent to be sent with any http request (see http://developer.github.com/v3/#user-agent-required )

The problem is that the function
function url_get
in /mantis/core/url_api.php does not provide a user agent string.

I did a very crude hack that basically enforces CURL and sets a user agent
like this:

if( !ini_get_bool( 'allow_url_fopen' ) ) { // disable file_get_contents
    return @file_get_contents( $p_url );
}
# Use the PHP cURL extension
if( function_exists( 'curl_init' ) ) {
    $t_curl = curl_init( $p_url );
    curl_setopt($t_curl,CURLOPT_USERAGENT,'Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13'); // Set a user agent
    curl_setopt( $t_curl, CURLOPT_RETURNTRANSFER, true );

    $t_data = curl_exec( $t_curl );
    curl_close( $t_curl );
    return $t_data;
}

I'd recommend to either change the Mantis API or use your own function url_get in the Source plugin.

Thank you for a great plugin.

Hi, I get the following error when importing :

APPLICATION ERROR #401
Database query failed. Error received from database was #1062: Duplicate entry '8673-1136' for key 1 for the query: INSERT INTO mantis_plugin_Source_bug_table ( change_id, bug_id ) VALUES (?, ?), (?, ?), (?, ?), (?, ?).

all I changed is the regexp as follows:
svn commit message is: "[FFT-00012345] blah blah"

Bug Link Regex Pass 1 : /[FFT-(\d_)1-9].*/i
Bug Link Regex Pass 2 : /(\d+)/

has anyone seen this message before ?
thanks !

The plugin always sets a fixed issue's status to Resolved, regardless of how the the "Resolve Fixed Issues" option (plugin_Source_enable_resolving) is set in the config page.

Windows 7 Prof SP1(32) - All Updates/Fixes applied (Locale: de-DE)
IIS 7.5
PHP 5.4.18
MantisBT 1.2.15 (Locale: Default)
SI-Plugins (VCS 0.18, SVN 0.16, WebSVN 0.17)
WebSVN 2.3.3
SQLServer Express 2012 (SP1)
Subversion 1.8.1
TortoiseSVN 1.8.1

I tried the version as of 20130820 (with xml patch) to get my issue (#62) with german umlauts solved.

With this version my custom post-commit hook, which notifies MantisBT about the commit, no longer works(http post -> ..../plugin.php?page=Source/checkin).

At least neither a changeset nor a bug_note for resolved issues (state isn't change either) is added to the db.

A diff between my working version(20130305) and the tested shows only relevant changes in SourceSVN.php. My knowledge of PHP isn't sufficient to figure out what's going wrong here.

And please increment the version number of the module

On Windows I'm getting the following error when I try to Import Latest Data:

svn: E125001: Can't determine the user's config path

I tried setting the --config-dir argument in the config page, but it looks like this isn't being used in check_svn() to test with svn help.

I am running a Mantis instance which hosts different projects with different users and different permissions, but all repositories are visible to everyone.

It would be nice to be able to assign a repository to a project, and then have the project permissions apply for the repository as well.

Commits authored by someone without write access to repository and/or without being developer in MantisBT are not registered properly in the MantisBT history, as shown in the issue below

http://www.mantisbt.org/bugs/view.php?id=14700&history=1#history

In this example, the commit was authored by "JGuilbaud" aka LapinKiller in MantisBT, and committed by me.

• Changeset attach event is logged by non-existent user id '0'
• Issue fields updates are done by 'anonymous' user

Date Modified    Username       Field                    Change               
====================================================================== 
[...snip...]
2012-09-10 09:29 user0          Changeset attached        => MantisBT
master-1.2.x 7aa07d86
2012-09-10 09:29 anonymous      Status                   assigned => resolved
2012-09-10 09:29 anonymous      Resolution               open => fixed       
2012-09-10 09:29 anonymous      Fixed in Version          => 1.2.x           
======================================================================

I believe the author should be the committer.

So I have everything working great, but I'm a little confused on this.

When I was testing, it seemed that imports happened automatically. But a colleague just push, and the import didn't happen. I ran import latest data, and his changes came in successfully.

Does the import need to be automated? If so, do you have any recommendations for the setup (I was going to use wget from Jenkins... do you have a different approach?)

Specifically, certain members of our development team insist on committing, testing the autobuild executables, then changing their commit messages to indicate fixes (rather than "speculating" on fixes beforehand). I currently can't see a way to have the SCI plugin(s) parse the revprop changes and update the already imported changeset logs. Is this even do-able with the current plugins?

Running SCI 0.18, SVN-I 0.16, WebSVN-I 0.17 against MantisBT 1.2.15 on Ubuntu 10.04 LTS

Do I understand correctly, that it is impossible to access the information provided by plugin from SOAP?
What I would like to do, is to get the list of changesets attached to issue using any easy parsable form (JSON, SOAP...)

Hello,

I'm facing a problem when I try to import a kind of big repository for the first time with the source-integration-plugin for Github.
I've just installed the newest version of mantis, applied the patch to get it working together with SourceGithub and tried to do a complete import of one of my repositories.

But after around 60s my provider ends the process.
This leads in some cases to a new project enry named "Imported ....current date&time". And in some other cases (if I only import som special branches), the commits of these branches are imported but now connection between the issues and the commits are made.

Any idea how I can solve that problem for me? Is it possible to break the import process into smaller pieces?

Regards,
Michael

I'd like to use the Source plugin (only - don't need the others) to connect to existing repositories on my server. When I use the Mantis interface where the repository is created, where are the actual files? I'd like to know where they are so I can issue a 'git clone' in that directory and just have the web interface see the repositories that I've copied over to the server.

Source Control Integration Plugin does not respect the custom email notifications configured for a particular project.

For example, consider a project has an Email Notification Configuration which allows all the Developers(role) to receive email notifications when an issue is Resolved. The notifications are NOT sent to Developers and only the reporter and administrators receives the notification.

However, the notifications are sent to Developers when an issue is resolved through the Mantis Web Interface.

Is it possible to integrating Mantis with Gitlab? I see no available plugin yet.

Two problems:

The first is already reported by issue #24, and it is fixed by purposed fix for issue #24 (#25)

The second is that after applying that fix, and doing import, the changesets does not appear correctly - the left side of the "changesets" view does work (showing author, timestamp, etc') but the right side (showing commit message etc') does not (appears empty)

Please Help ? ?

Hi,

When "View Threshold" is set to "developer", user with access level "reporter" can't see the changesets, good. However they can see them indirectly in the history with a quite explicit message. I expect them to see no informations about commits.

For reference in order to hard code this behavior for this configuration, I added the following code in history_get_raw_events_array in core/history_api.php

if( $v_type == PLUGIN_HISTORY && ($v_field_name == "Source_changeset_attached" || $v_field_name == "Source_changeset_removed")) {
          if( !$t_private_bugnote_visible ) {
                        continue;
              }
   }

Maybe Github API has been changed.

Import data (either latest or everything) fails. The reason is that (at present) list of all commits can't be gotten from "https://api.google.com/repos/user/repo/commits/". The last slash should be removed, i.e. the right url for list of all commits is "https://api.google.com/repos/user/repo/commits".

Tiny change in code could fix it.

In file SourceIntegration.php, function displayBug, line 36, you use function access_has_global_level to know if you should display changeset.

This fails if global access is not the same than project access.

The function access_has_project_level should be used instead.

This bug report follows bug #36 ; I found some others incomptabilities with SQL Server

config : MantisBT 1.2.12 with SQL Server 2008
plugin-version : master (changeset 2a0e94b)

1° Error when searching issues (Repositories > Search ; search for all changesets) saying that c.timestamp field is not in a aggregate function
query :

SELECT COUNT(c.id) 
FROM mantis_plugin_Source_changeset_table AS c 
LEFT JOIN mantis_plugin_Source_repository_table AS r ON c.repo_id=r.id
ORDER BY c.timestamp DESC

This is caused by ORDER BY clause at the end of query

2° Again when searching issues --> error cannot compare TEXT fields
query :

SELECT DISTINCT( c.id ), c.* 
FROM mantis_plugin_Source_changeset_table
 AS c LEFT JOIN mantis_plugin_Source_repository_table AS r 
 ON c.repo_id=r.id ORDER BY c.timestamp DESC

This is caused by DISTINCT clause.

My workarounds / solutions :
1° move $t_order variable from Source_Process_Filters(..) to find(..) function. The find(..) function becomes :

list( $t_filters, $t_filter_params ) = Source_Twomap( 'Source_Process_FilterOption', $this->filters );
list ( $t_query_tail, $t_params ) = Source_Process_Filters( $t_filters, $t_filter_params );
$t_order = 'ORDER BY c.timestamp DESC';

$t_count_query = "SELECT COUNT(c.id) $t_query_tail";
$t_full_query = "SELECT DISTINCT( c.id ), c.* $t_query_tail $t_order";
# ...

2° Simply delete DISTINCT keyword (seem not useful here) ini Source.FilterAPI.php, function find

I'm not able to clone the folder, instead I get this:

Is the repository working?

Any change to get BitBucket.org running with an existing plugin? Github maybe?

Windows 7 Prof SP1(32) - All Updates/Fixes applied (Locale: de-DE)
IIS 7.5
PHP 5.4.9
MantisBT 1.2.15 (Locale: Default)
SI-Plugins (VCS 0.18, SVN 0.16, WebSVN 0.17)
WebSVN 2.3.3
SQLServer Express 2012 (SP1)
Subversion 1.7.9
TortoiseSVN 1.7.12

Perhaps that's not an issue at all, but due to my current configuration.
For all change sets, whenever the log message contains German Umlauts the message don't show up in the views.
I'd edited some of them in the db(mantis_plugin_Source_changeset_table) directly ('ä' -> 'ae'...) and those are displayed.

LG M.

Source Integration lacks current installation & usage instructions. All the examples from leetcode.net/noswap.com are outdated and now that Source Integration is no longer being actively maintained by @jreese, it seems appropriate to update the README and start pulling documentation into the repository.

In MantisBT 1.3, the db_query() function will be removed from the API (see mantisbt/mantisbt#128).
The following occurences have been found in this plugin; they should be replaced
by db_query_bound() calls

Source/Source.API.php:718:      $t_result = db_query( $t_query );
Source/Source.API.php:793:      $t_result = db_query( $t_query );
Source/Source.API.php:1528:     $t_result = db_query( $t_query );

For some reason, Cgit imports all revisions of my project up to a particular revision, and any attempt to import newer data (using "Import Latest Data" from the Manage Repositories interface, or using the post-receive hook below)

#!/bin/sh

curl "http://localhost/issues/plugin.php?page=Source/import&id=allapi_key=MY_API_KEY"

results in this message:

Oldest 'master' branch parent: ''
Retrieving master ... processing fdeca4274efd46b4122c3b2cecedb0c06a12019d ... already exists.

I've tried deleting the repository configuration and re-creating it and it's stuck at the same revision.

If I pick "Import Everything" I get some "already exists" message as well, for example

Retrieving 2a1973c8be416890722f5a275a761787e0bdca87 ... processing 2a1973c8be416890722f5a275a761787e0bdca87 ... already exists.

interspersed among the normal ones, ending with the same revision as when updating

Retrieving 09afc275dc6841b92c6e6ffe980bc6d02f5ca25b ... processing 09afc275dc6841b92c6e6ffe980bc6d02f5ca25b ... saved.

Oldest 'master' branch parent: ''
Retrieving master ... processing fdeca4274efd46b4122c3b2cecedb0c06a12019d ... already exists.

The various regexp for importing the change sets via SourceGitweb should be depended on the version of gitweb used. This would save a lot of adjustments.