All geek questions in one place

Best practices for integrating Mantis and Subversion

I would like to integrate Subversion into Mantis, so when I do a subversion commit, the corresponding Mantis problem is updated. With Mantis' Source Integration Plugin, it becomes a cinch to exit using WebSVN. However, none of the documentation I read clearly explains: a) what exactly is the relationship between websvn and Mantis Integration, or b) what security implications exist for configurations other than simple repositories without access control.

Most suitable web pages that I read:

In short, I restrainedly give Mantis the keys to Subversion without fully understanding the implications.

+4
source share
2 answers

Integration works as follows:

  • The user opens the problem.
  • The developer performs a commit, providing the problem number in his comment.
  • Mantis now knows about commit and tries to get svn metadata
  • Mantis stores metadata internally and associates versions with issues based on commit comments.
  • You can also manually link issues with versions.

What you need to know:

  • You need to set read permissions in all of your repositories for which the mantis user will connect to svn.
  • Anyone who has access to your configuration file can use the saved user / password to access the svn repository.
  • Anyone who has access to your praying mantis database can see complete statistics and details about all commits made in svn (files, users, comments, etc.).
  • The proposed hook after fixing only tells the mantis that there is a new version
  • The plugin has a list of allowed / forbidden servers, which prohibits / allows hosts to connect to your repository.
  • You can also configure https / ssl for both servers (setting up ssl keys is a bit more complicated)

I have used this setting for a long time and it works like a charm.

I also suggest using websvn, as this is the best way to instantly see the differences, in one click from the mantis problem

I hope I helped

J.

+4
source

mantis svn integration

download the plugin from https://github.com/mantisbt-plugins/source-integration

Copy Source and SourceSVN to mantism plugins

install source and source SVN plugins in mantis

install "API KEY" on the Source plugin

set "Corrected state fix" to "enabled"

set “Bug fix fixed” to “fixed”

add the repository [your repository] to the svn source

install post-hook on svn server, if you use beanstalkapp, it's simple, just add url for post-mapping:

http: // [your mantis server] /mantis/plugin.php?page=Source/import&id=all&api_key= [your api key]

(if you cannot do svn hook, you can run cron curl)

therefore, we must format the comment when sending SVN codes:

link to the question:

issue # [issue id] [another short comment]

eg. issue # 0005480 test link problem

it will link the set of changes to release and add comments to the release

fixed problem:

fixed # [issue id] [another short comment]

eg. fixed # 0005480 fixed fixing the problem

it will link the set of changes for the release, add a comment to the problem, and set the status of the problem for troubleshooting.

so all you need is to write the correct comment and not copy svn files, open a browser, write notes about problems, set the status of the problem ...

everything will be done by plugins and svn server (beansapptalk)!

I wrote this on my blog

+5
source

Source: https://habr.com/ru/post/1496867/

More articles:


All Articles