Does FogBugz 6 support integration with multiple source control systems?
FogBugz 7 supports multiple repositories, just create them in
FogBugz has a very open and configurable source control integration system. Many users might have multiple repositories or multiple systems and they want to know how to set it up so FogBugz can link to all of them.
FogBugz 6.1 and higher supports multiple repositories within a single source control system. This will even work for FogBugz On Demand users, unlike the other suggestion below. FogBugz 6.1 added the sRepo field to the CVS table for FogBugz which can be used in the Source Control URLs. To do so, add the sRepo argument to the trigger script for your source control system (on the line where the URL with sFile and sPrev and sNew is constructed). To refer to the sRepo value in the Source Control URL, use ^REPO. For instance, if you were using Mercurial and entered the fully-qualified repository URL as sRepo, then the corresponding Source Control URL for logs would be: ^REPO/log/^R2/^FILE
If you are running FogBugz on your Server, or are using multiple source control systems, another way to do this is to have a director script gather your FogBugz requests when you click on links and figure out where to send the user to, based on the repository of that checked in file. This method will work on FogBugz 4 and higher.
Example for two Source Control Systems
What I found differs from above a little. This is with FogBugz 6 with Subversion on Ubuntu 9.10 through Apache with WebSVN 2.2.1
I added the repository name to the two urls
and changed the URLs in
to work with my version of WebSVN. I also made
The only thing left then was to ensue that the repository made it into the redirect URL