most recent 30 from http://fogbugz.stackexchange.com 2013-05-22T07:26:05Z http://fogbugz.stackexchange.com/feeds/question/4433 http://www.creativecommons.org/licenses/by-nc/2.5/rdf http://fogbugz.stackexchange.com/questions/4433/mercurial-integration FogBugz FAQ 2010-09-07T20:45:36Z 2012-10-18T21:50:54Z

<p>How do we set up Mercurial source control integration?</p>

http://fogbugz.stackexchange.com/questions/4433/mercurial-integration/4434#4434 FogBugz FAQ 2010-09-07T20:46:46Z 2010-09-07T20:46:46Z

<h2>Getting Mercurial to transmit changes to FogBugz</h2> <p>To setup Mercurial-FogBugz integration, start by logging into FogBugz as an administrator and going to <strong>Admin | Source Control</strong>. Click <strong>Create New Repository</strong>. In the resulting dialog, select <strong>Mercurial</strong> as the type and click <strong>Next</strong>.</p> <p>In the resulting dialog, download the Python script and place it anywhere that's visible to the Mercurial server process. It should <strong>not</strong> be in your hgext directory.</p> <p>To enable the script, edit the .hg/hgrc file in your repository by adding the following lines:</p> <pre><code>[hooks] changegroup = python:/path/to/fogbugz.py:hook </code></pre> <p>You will then need to configure the FogBugz extension so that it knows where to locate your FogBugz install. Simply add the following lines, edited appropriately, into your .hg/hgrc file:</p> <pre><code>[fogbugz] host=http://full/path/to/fogbugz </code></pre> <p>Finally, you should set your baseurl to make sure that the appropriate repository location is passed along to FogBugz. Baseurl is the web URL to where the "hg serve" web server is running for the provided repository.</p> <pre><code>[web] baseurl=http://url/of/your/repo </code></pre> <h2>Getting FogBugz to Provide Hyperlinks to Mercurial</h2> <p>Assuming you supplied the right value for <strong>baseurl</strong> in your hgrc file, FogBugz will automatically link to logs and diffs in Mercurial. If you do not have hg serve running, then although FogBugz will record changesets, the links back from FogBugz will not point anywhere meaningful.</p>

http://fogbugz.stackexchange.com/questions/4433/mercurial-integration/4550#4550 Nick Pierpoint 2010-09-11T12:40:56Z 2010-09-11T12:40:56Z

<p>Our central Mercurial repository sits on a server that has no internet access to our On Demand FogBugz instance, so the <a href="http://fogbugz.stackexchange.com/questions/4433/how-do-we-set-up-mercurial-source-control-integration/4434#4434" rel="nofollow">standard approach</a> didn't work for us. Instead, we use the <strong>outgoing</strong> hook in each <strong>local</strong> repository.</p> <p>For example:</p> <pre><code>[hooks] outgoing = python:C:\Program Files\FogBugz\fogbugz.py:hook [fogbugz] host=https://xxx.fogbugz.com [web] baseurl=http://xxx:8000 </code></pre>

http://fogbugz.stackexchange.com/questions/4433/mercurial-integration/10884#10884 Terence 2012-10-18T21:50:54Z 2012-10-18T21:50:54Z

<p>If my baseurl is https and secured with a password, how do I store the credentials required?</p>