User information
 Loading ...
Show article in Knowledge Base

 Git integration Export knowledge base Export     SubscribeSubscribe      Show article info

With the VCS and source code integration support in VisionFlow you can view the commits that has been done for each issue into your Git repository.


In the Edit issue page you can see the commits that has been done for an issue as shown below. All links in the view can be customized to work with your Git viewer. The predefined links are optimized for GitWeb.


VisionFlow Documentation/other/git-issues.png


To enable VCS integration you'll need to:

  1. Install the latest Java runtime on the subversion machine available here
  2. Download the Java committer classes zip-file available here, and extract it somewhere on your server
  3. Add a post-receive hook available here, rename it to 'post-receive' and put it into the git hooks folder on your server
  4. Change the post-receive hook script according to your needs, more specifically the fields below:      
    • REF_ID_HASH= (this is the id reference found at the bottom i the SVN section on the settings page on the project. Note: the reference is global for your account so every project uses the same id reference)
    • HTTP_POST_URL="" (*.do is a struts-action and not an actual file). If you are running the installed version then should be replaced with your own server URL
    • PATH_FOR_JAVA_HOOK_CLASS="D:/git/repos/project.git/.git/hooks" (your path here)
    • LOG_FILE_PATH="$PATH_FOR_JAVA_HOOK_CLASS/commits_to_post"
    • Replace REPOSITORY_NAME_HERE with your repository in this line: echo "$(git log -1 --decorate=full --pretty=format:"%H%n%ce%n%ci%nREPOSITORY_NAME_HERE%n%B%n----" $rev)" >> $TXN_FILE_NAME
  5. Configure VCS integration in the project settings as shown below


VisionFlow Documentation/other/git-config.png


 Check the Enable VCS integration to allow the VCS tool to POST commits to VisionFlow.


 Enter the repository name for your repository. Please note that it is important that the name 
specified matches your repository name exactly as this will be used elsewhere in the system and 
in the links where [$repository-name$] is specified.


 Choose your viewer type. GitWeb paths are predefined but you can change any 
of the paths to match your viewer web application.

All special tokens are replaced at run-time with the correct values according to

  • [$repository-name$] - The repository name you've specified in the repository name field
  • [$repository-path$] - The repository path you've specified in the repository path field
  • [$path$] - The path committed by the VCS, such as "YourRepoName/trunk/"
  • [$rev$] - The revision when the file was committed
  • [$rev-1$] - The previous revision compared to when the file was committed


 Specify the issue key formats you want to use for identifying the issue key in the comment 
when committing files into the repository.

For example: You commit some files, such as, into the repository 
and with the following comment "Fixed [WEB-123] and [WEB-223] payment related bugs
indicating what bugs you have fixed

By doing this VisionFlow can identify the issues to add this commit information to, however your 
comment could also be "Fixed {WEB-123} and {WEB-223} payment related bugs" or 
"Fixed #WEB-123 and #WEB-223 payment related bugs" depending on what you specify in the 
issue key formats


 It is also important that the IssueKeys are unique per project in your account for the SVN integration to work, i.e. there can't be any duplicate IssueKeys, so choose your IssueKey prefixes with care.

User comments
 Loading ...