most recent 30 from http://fogbugz.stackexchange.com 2013-05-21T23:46:17Z http://fogbugz.stackexchange.com/feeds/question/4402 http://www.creativecommons.org/licenses/by-nc/2.5/rdf http://fogbugz.stackexchange.com/questions/4402/source-code-control-system-integration FogBugz FAQ 2010-09-07T18:57:26Z 2012-10-12T21:02:26Z

<p>Can we get an overview of FogBugz's Source Control Integration feature?</p>

http://fogbugz.stackexchange.com/questions/4402/source-code-control-system-integration/4439#4439 FogBugz FAQ 2010-09-07T21:05:14Z 2012-10-12T21:02:26Z

<p>FogBugz can be set up to work together tightly with most source control systems. When you commit a bug fix to source control, you simply type the case number that you're fixing. The integration scripts see this and create bidirectional links:</p> <ol> <li>From the FogBugz case to the source control history and diffs</li> <li>From the source control system to the FogBugz case.</li> </ol> <p>The benefits:</p> <ul> <li>You can implement a code-review process. Simply assign a case to the code reviewer. They click on the links to see the diffs in the source control system and review them.</li> <li>It's easy to find out how a bug was fixed by jumping straight to the source code change.</li> <li>When you're looking at the changes made in the source code and wondering why they were made, you can quickly jump to the bug they were intended to fix.</li> </ul> <p>The exact mechanism for entering a case number when you commit changes depends on your source control system.</p> <ul> <li><a href="http://fogbugz.stackexchange.com/questions/4403/" rel="nofollow">Entering case numbers using CVS</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4405/" rel="nofollow">Entering case numbers using Subversion</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4408/" rel="nofollow">Entering case numbers using TortoiseSVN</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4410/" rel="nofollow">Entering case numbers using Perforce</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4413/" rel="nofollow">Entering case numbers using Visual SourceSafe</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4415/" rel="nofollow">Entering case numbers using SourceGear Vault</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4417/" rel="nofollow">Entering case numbers using Mercurial</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4419/" rel="nofollow">Entering case numbers using Team Foundation Server</a></li> </ul> <p>Before you can start using source control integration, you will need to make a few configuration changes to FogBugz and your source control system so they can talk to each other.</p> <ul> <li><a href="http://fogbugz.stackexchange.com/questions/4421/" rel="nofollow">Setting up CVS</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4423/" rel="nofollow">Setting up Subversion</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4424/" rel="nofollow">Setting up TortoiseSVN</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4427/" rel="nofollow">Setting up Perforce</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4429/" rel="nofollow">Setting up Visual SourceSafe</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4431/" rel="nofollow">Setting up SourceGear Vault</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4433/" rel="nofollow">Setting up Mercurial</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4435/" rel="nofollow">Setting up Team Foundation Server</a></li> <li><a href="http://fogbugz.stackexchange.com/questions/4437/" rel="nofollow">Generic instructions for other source code control systems</a></li> </ul> <p>If you don't already have source control, we recommend <a href="http://fogcreek.com/kiln/" rel="nofollow">Kiln</a>.</p> <h2>Using Source Control Integration</h2> <p>When you have everything setup, source control integration in FogBugz allows you to associated changes you commit with a given case or cases. When you commit your changes in VCS, your hook script will look for something in your commit message that gives it a case number. For the scripts we distribute, the format is "BugzID: XYZ" where XYZ is a case number. The hook script then posts the info to FogBugz.</p> <p>When you look at the case you referenced (number XYZ) in FogBugz, you will see a link on the left side of the case, "checkins".</p> <p><img src="http://our.fogbugz.com/default.asp?pg=pgDownload&amp;pgType=pgWikiAttachment&amp;ixAttachment=206345&amp;sFileName=checkins%20link.png" alt="alt text"></p> <p>When you click the link, a pop-up dialog appears, showing all of the files and revisions committed against the case.</p> <p><img src="http://our.fogbugz.com/default.asp?pg=pgDownload&amp;pgType=pgWikiAttachment&amp;ixAttachment=206346&amp;sFileName=checkins%20dialog.png" alt="alt text"></p> <p>Based on your configured URLs in Admin -> Source Control, the file paths and revision numbers will link to an external system to show you file and diff views.</p>