Integrating Fogbugz with TortoiseSVN without URL/Subversion backend

I've obtained TotroiseSVN mounted and also have a bulk of my databases signing in and also of C :\ subversion \ and also a pair monitoring in and also out from a network share (I forgot this when I initially uploaded this inquiry) .

This suggests that I do not have a "subversion" web server per - se.

Just how do I incorporate TortoiseSVN and also Fogbugz?

Edit : put italics

0
2019-05-09 11:00:02
Source Share
Answers: 4

The trouble is that FogBugz will certainly link to a website, and also file:/// etc is not a website. To get integration 2 means, you require an internet server for your subversion database. Either set up Apache or another thing that can organize those points the correct means.

0
2019-05-31 04:36:21
Source

Why can not you merely install a subversion web server? If you download and install VisualSVN Server, which is free, you get a http web server for your resource code and also can hence make use of the FogBugz manuscripts for incorporating both.

The factor I'm asking is due to the fact that all manuscripts and also documents until now thinks you have the web server, customer - side manuscripts are also new for FogBugz to have layouts for them so you are virtually entrusted to your very own tools on that particular.

0
2019-05-17 20:24:47
Source

I am not exactly sure I follow you. Do you have the databases on the network or on your C :\ drive? According to 2 of your blog posts, you have both, or neither, or among them or ...

You can not get VisualSVN or Apache to securely offer databases from a network share. Given that you initially claimed you had the databases on your C :\ drive, that is what you get suggestions for. If you have a various arrangement, you require to inform us concerning that.

If you have the databases on your neighborhood harddisk, I would certainly install VisualSVN, or incorporate it right into Apache. VisualSVN can run great along with Apache so if you perform you just need to install it. Your existing databases can additionally simply be replicated right into the repository origin directory site of VisualSVN and also you are up and also running.

I am unclear why that large blog post below is classified as insufficient, as it information the actions essential to set up a hook manuscript to educate FogBugz concerning the new alterations connected to the instances, which need to be what the insufficient message claims it does not do. Is that not functioning?

0
2019-05-17 20:24:07
Source

This solution is insufficient and also mistaken! It just functions from TortoisSVN to Fogbugz, yet not vice versa. I still require to recognize just how to get it to function in reverse from Fogbugz (like it's made to) to make sure that I can see the Revision number a bug is resolved in from Fogbugz while considering a bug.


Handy URLS

http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-propertypage.html

http://tortoisesvn.net/issuetracker_integration


Set the "Hooks"

  1. Go right into your fogbugz account and also click Extras > Configure Source Control Integration

  2. Download "post - commit.bat" and also the VBScript apply for Subversion

  3. Create a "hooks" directory site in an usual conveniently accessed area (ideally without rooms in the documents course)

  4. Place a duplicate of the documents in the hooks directory sites

  5. Rename the documents without the ". secure" expansion

  6. Right click any kind of directory site.

  7. Select "TortoiseSVN > Settings" (in the appropriate click menu from the last action)

  8. Select "Hook Scripts"

  1. Click "Add"

  2. Set the buildings hence :

    • Hook Type : Post - Commit Hook

    • Working Copy Path : C :\ \ Projects (or whatever your origin directory site for every one of your tasks is. If you have numerous you will certainly require to do this action each.)

    • Command Line To Execute : C :\ \ subversion \ \ hooks \ \ post - commit.bat (this requires to indicate any place you place your hooks directory site from action 3)

    • I additionally picked the checkbox to Wait for the manuscript to end up ...

WARNING : Don't neglect the double back - lower! "\ "

Click OK ...

Note : the screenshot is various, adhere to the message for the documents courses, NOT the screenshot ...

At this factor presumably you can click "Issue Tracker Integration" and also select Fogbugz. no way. It simply returns "There are no concern - tracker carriers readily available".

  1. Click "ALRIGHT" to close the entire setups discussion window

Configure the Properties

< ol start = "2" >
  • Once once more, Right click the origin directory site of the looked into task you intend to collaborate with (you require to do this "set up the buildings" action for each and every task - - See "Migrating Properties Between Projects" listed below)

  • Select "TortoiseSVN > Properties" (in the appropriate click menu from the last action)

  • Add 5 building value sets by clicking "New ..." and also putting the adhering to in "Property Name" and also " Property Value" specifically :

  • bugtraq :tag BugzID :
    bugtraq :message BugzID : %% BUGID%%

    bugtraq :number real

    bugtraq :link http://[your fogbugz URL below ]/ default.asp?% BUGID%

    bugtraq :warnifnoissue incorrect

    .

    < ol start = "15" >
  • Click "OK"
  • Commiting Changes and also Viewing the Logs

    Now when you are devoting, you can define one bug that the devote addresses. This sort of pressures you to devote after dealing with each bug ...

    When you watch the log (Right click origin of task, TortoiseSVN > show log) you can see the bug id that each examining represents (1), and also you can click the bug id number to be required to fogbugz to watch that bug instantly if you are considering the real log message. Pretty great!


    Migrating Properties Between Projects

    1. Right click a task that currently has the correct Properties configuration

    2. Select "TortoiseSVN > Properties" (from the appropriate - click menu from action 1)

    3. Highlight every one of the wanted buildings

    4. Click "Export"

    5. Name the documents after the building, and also area in a conveniently obtainable directory site (I positioned my own with the hooks documents)

    < ol start = "5" >
  • Right click the origin directory site of the looked into task requiring buildings set for.

  • Click "Import"

  • Select the documents you exported symphonious 4 over

  • Click Open

  • 0
    2019-05-10 05:26:01
    Source

    Related questions