BugTracker.NET Documentation

 

  • BugTracker.NET Home

  • Documentation Home

     

     

    Is BugTracker.NET helping you? Donate!

     

  • sponsors
    Axosoft OnTime 2008
    A bug tracker, project wiki, requirements manager, and help desk solution that manages the development process so developers can focus on coding. Windows, Web, and VS.NET interfaces. Free single-user licences and 30-day Team Trials

    Gemini Project Issue Tracking
    Clear and Easy Issue Management. Track and manage projects with tools that set the standard for the industry. Best of all, the 5 User License is FREE!
    Learn More...

    JIRA 3.12.3 - Free Evaluation License
    Brilliantly Simple, Incredibly Powerful bug and issue tracking software used by more than 8,700 organizations in over 97 countries.
    Get your free evaluation copy now.

     

    Subversion Integration   [back to contents]

    If you are not using a version control system, you should start today. A good choice would be Subversion, along with its excellent Windows client TortoiseSVN. BugTracker.NET has built-in support for integration with Subversion. The files you need for the integration are all in the btnet\subversion folder.

     

    Installation

    To enable the integration, there are two easy steps:

      1. Connect your Subversion server to BugTracker.NET's database
      2. Connect BugTracker.NET to your Subversion server.

    1. To connect Subversion to BugTracker.NET's database, you copy and edit a "hook" script:

      * Copy the file "btnet_post_commit.rename_to_vbs" into the "hooks" folder of your Subversion repository.

      * Open the file in a text editor, like Notepad, and edit it according to the instructions in the file itself. You probably will only need to change the connection string to your SQL Server database. There are troubleshooting tips documented in the script itself.

    2. To connect BugTracker.NET to your Subversion server, edit the following settings in your Web.config. You might only need to edit the "SubversionRepositoryUrl" setting.

      <add key="EnableSubversionIntegration" value="1"/>
      <add key="SubversionRepositoryUrl" value="svn://127.0.0.1/svnrepos"/>
      <add key="SubversionPathToSvn" value="svn.exe"/>
      <add key="SubversionUsername" value=""/>
      <add key="SubversionPassword" value=""/>

     

    When you commit a change, simply type in the BugTracker.NET bug id as the first characters in the checkin comment. Subversion will execute the hook script. The hook scrit will use the bug id in the comment to associate the checkins with the bug.

    There are some optional steps you could take to make the integration even nicer. If you use the "TortoiseSVN_integration.bat" from the subversion folder to set the Subversion "bugtraq" properties, then instead of having to enter the BugTracker.NET id at the start of each comments, TortoiseSVN displays a control in the upper right. (see screenshots below). It will even warn you if you have forgetten to enter a number in the field.

    Still another option is to link BugTracker.NET with the web pages of a browser-based Subversion client like "WebSvn". See the "WebSvnUrl" setting in Web.config for information.

     

    Troubleshooting

    Setting up a subversion server is VERY easy, but one area I personally stumbled with was with paths, pointing to a child when I should have been pointing to a parent. Here is an example showing what works.

    To create a repository:

    C:\>svnadmin create c:\my_parent_folder\my_repository_folder

    To start a Subversion server. You could have several repositories under "my_parent_folder":

    C:\>svnserve -d -r c:\my_parent_folder

    BugTracker.NET's Web.config setting:
    <add key="SubversionRepositoryUrl" value="svn://127.0.0.1/my_repository_folder"/>

     

    Using Subversion Integration

    The following screenshots demonstrate what Subversion integration looks like in BugTracker.NET assuming you have everything configured correctly.

     

    Doing a commit (checkin) using TortoiseSVN:

     

    Enter the BugTracker.NET bug id, "222", in the comment text:

     

    Subversion confirms the commit. It was Subversion revision #63:

     

    The bug in BugTracker.NET. We changed two files, so there are two revision lines associated with this bug:

     

    If you click "revisions" above, you see the Subversion file revisions related to the bug:

     

    Run a "diff" to see what changed:

     

    View file history, diff between any two versions:

     

    View an annotated copy of the file, showing who changed each line and when:

     
     


    Corey Trager
    ctrager@yahoo.com
    http://ifdefined.com.