-
New Feature
-
Resolution: Fixed
-
Critical
-
None
Currently, the Subversion Merge plug-in lacks the ability to provide a commit comment. For my particular setup, Subversion has pre-commit hooks to JIRA to check whether a valid issue from the user is being used. When I attempt to create a branch using the plug-in, the job fails with a similar error message as follows (removed confidential info):
svn: Commit failed (details follow): svn: Commit blocked by pre-commit hook (exit code 4) with output: JIRA issue Created was not found on <JIRA-server>, commit aborted. JIRA issues are case sensitive and must be entered in UPPER case. Valid issues for <user> include;
<issue-list>
In this case, each of the feature that makes a svn merge call should take a commit message option. In addition, I also question how the plug-in detects the user performing the merge command. Should a user name and password be supplied to svn commands that write? Perhaps this is also a requirement for a secured Subversion scenario.
These might not be bugs, but they would be critical features for some folks to take advantage of this plug-in. Please consider providing them and let me know if you have any questions about my scenarios. Thanks a lot!