Creating Mercurial User Repositories

  • Revision slug: Creating_Mercurial_User_Repositories
  • Revision title: Creating Mercurial User Repositories
  • Revision id: 52571
  • Created:
  • Creator: Yoric
  • Is current revision? No
  • Comment 8 words added

Revision Content

 

When working with Mercurial, it is often nice to publish your changes on a server so others can examine and work with them as well. If you have commit access to CVS, you should have an LDAP account, and that should allow you to push to hg.mozilla.org. If you do, you can create clones in the /users directory and share them with others.

Configuring ssh

So you don't need to type your username every time, add these lines to ~/.ssh/config:

Host hg.mozilla.org
User your-hg@username.domain

where 'your-hg@username.domain' is simply your CVS username with the "%" character replaced with the "@" character.

Creating a Repository

It is a relatively easy process to create your own repository. It will be visible via HTTP at http://hg.mozilla.org/users/your-hg_...omain/my-repo1.

To do this, run the following command. Use the same command regardless of whether you want to clone an existing repository or create a new, empty one.

ssh hg.mozilla.org clone my-repo1

my-repo1 is the name of the new repository you want to create, not the repository you are trying to clone from.

Running the above ssh command will run an interactive script, prompting you to make some choices (about which repository you want to clone from). It is by and large self-explanatory. When the script is finished, ssh will exit. After 5-10 minutes, your repository should appear on http://hg.mozilla.org/users/

Editing your personal repository

Once you have created your mercurial repository, you can edit its description. This description will show up when people visit http://hg.mozilla.org/users/your-hg_username.domain. The process is similar to creating a brand new repository, instead of using the clone action, use the "edit" action. The "edit" action also lets you delete your repository. Please note that the delete action is irreversible.

~ $ssh hg.mozilla.org edit my-repo1

0) Exit.
1) Delete the repository.
2) Edit the description.

What would you like to do? 0

Creating an Mq Patch Queue Repository

Here's how to publish an Mq patch-queue repository:

  1. Create a new empty repository (say, "my-repo-patches") on hg.mozilla.org, as directed above.
  2. Verify that the repository is visible at http://hg.mozilla.org/users/your-hg_...y-repo-patches
  3. Initialize a patch queue, if you haven't already, with hg qinit -c (option -c ensures that your patch queue is itself a hg repository)
  4. Create a hgrc for your patch queue (at .hg/patches/.hg/hgrc) with these contents:
    [paths]
    default = http://hg.mozilla.org/users/your-hg_username.domain/my-repo-patches
    default-push = ssh://hg.mozilla.org/users/your-hg_username.domain/my-repo-patches
    

Examining Clones Via the Web

It may take a while for your clone to show up because of some caching mechanisms that have been put in place. It should show up pretty quickly though, and you'll be able to browse history via a web interface.

Others can also pull changes via http:

hg clone http://hg.mozilla.org/users/your-hg_username.domain/my-repo1

Pushing Changes

To push changes, use ssh:

hg push ssh://hg.mozilla.org/users/your-hg_u...omain/my-repo1

Or, if you just want to push your patch queue:

cd .hg/patches
hg commit -m "Some message"
hg push ssh://hg.mozilla.org/users/your-hg_u...omain/my-repo1

In either case, you may also want to add that path to the repository's hgrc, so you don't have to type it every time. Put something like this in .hg/hgrc:

[paths]
default-push = ssh://hg.mozilla.org/users/your-hg_u...omain/my-repo1

Pulling your changes

You may wish to use this repository to share changes between machines. For this, start by doing the exact same setup on the other machine. In other words, if you have pulled mozilla-central from your first machine, pull it from the second machine. If you have created a queue on the first machine, create a queue on the second machine, etc.

Then, to pull the complete repo:

hg pull ssh://hg.mozilla.org/users/your-hg_u...omain/my-repo1

Or, to pull only the patch queue:

cd .hg/patches
hg pull ssh://hg.mozilla.org/users/your-hg_u...omain/my-repo1

Revision Source

<p> </p>
<p>When working with <a href="/en/Mercurial" title="en/Mercurial">Mercurial</a>, it is often nice to publish your changes on a server so others can examine and work with them as well. If you have commit access to CVS, you should have an LDAP account, and that should allow you to push to hg.mozilla.org. If you do, you can create clones in the <code>/users</code> directory and share them with others.</p>
<h3 name="Configuring_ssh">Configuring <code>ssh</code></h3>
<p>So you don't need to type your username every time, add these lines to <code>~/.ssh/config</code>:</p>
<pre>Host hg.mozilla.org
User your-hg@username.domain
</pre>
<p>where <a class=" link-mailto" href="mailto:'your-hg@username.domain" rel="freelink">'your-hg@username.domain</a>' is simply your CVS username with the "%" character replaced with the "@" character.</p>
<h3 name="Creating_a_Repository">Creating a Repository</h3>
<p>It is a relatively easy process to create your own repository. It will be visible via HTTP at <code><a class=" external" href="http://hg.mozilla.org/users/your-hg_username.domain/my-repo1" rel="freelink">http://hg.mozilla.org/users/your-hg_...omain/my-repo1</a></code>.</p>
<p>To do this, run the following command. Use the same command regardless of whether you want to clone an existing repository or create a new, empty one.</p>
<pre class="eval">ssh hg.mozilla.org clone my-repo1
</pre>
<p><code>my-repo1</code> is the name of the <strong>new repository you want to create</strong>, not the repository you are trying to clone from.</p>
<p>Running the above ssh command will run an interactive script, prompting you to make some choices (about which repository you want to clone from). It is by and large self-explanatory. When the script is finished, ssh will exit. After 5-10 minutes, your repository should appear on <code><a class=" external" href="http://hg.mozilla.org/users/" rel="freelink">http://hg.mozilla.org/users/</a></code></p>
<h3 name="Editing_your_personal_repository">Editing your personal repository</h3>
<p>Once you have created your mercurial repository, you can edit its description. This description will show up when people visit <a class=" external" href="http://hg.mozilla.org/users/your-hg_username.domain" rel="freelink">http://hg.mozilla.org/users/your-hg_username.domain</a>. The process is similar to creating a brand new repository, instead of using the clone action, use the "edit" action. The "edit" action also lets you delete your repository. Please note that the delete action is irreversible.</p>
<pre>~ $ssh hg.mozilla.org edit my-repo1

0) Exit.
1) Delete the repository.
2) Edit the description.

What would you like to do? 0
</pre>
<h3 name="Creating_an_Mq_Patch_Queue_Repository">Creating an Mq Patch Queue Repository</h3>
<p>Here's how to publish an Mq patch-queue repository:</p>
<ol> <li>Create a new empty repository (say, "<code>my-repo-patches</code>") on hg.mozilla.org, as directed above.</li> <li>Verify that the repository is visible at <a class=" external" href="http://hg.mozilla.org/users/your-hg_username.domain/my-repo-patches" rel="freelink">http://hg.mozilla.org/users/your-hg_...y-repo-patches</a></li> <li>Initialize a patch queue, if you haven't already, with <code>hg qinit -c </code>(option <code>-c</code> ensures that your patch queue is itself a hg repository)</li> <li>Create a hgrc for your patch queue (at <code>.hg/patches/.hg/hgrc</code>) with these contents: <pre>[paths]
default = http://hg.mozilla.org/users/your-hg_username.domain/my-repo-patches
default-push = ssh://hg.mozilla.org/users/your-hg_username.domain/my-repo-patches
</pre> </li>
</ol>
<h3 name="Examining_Clones_Via_the_Web">Examining Clones Via the Web</h3>
<p>It may take a while for your clone to show up because of some caching mechanisms that have been put in place. It should show up pretty quickly though, and you'll be able to browse history via a web interface.</p>
<p>Others can also pull changes via http:</p>
<pre>hg clone http://hg.mozilla.org/users/your-hg_username.domain/my-repo1
</pre>
<h3 name="Pushing_Changes">Pushing Changes</h3>
<p>To push changes, use ssh:</p>
<pre class="eval">hg push <a class=" external" href="ssh://hg.mozilla.org/users/your-hg_username.domain/my-repo1" rel="freelink">ssh://hg.mozilla.org/users/your-hg_u...omain/my-repo1</a>
</pre>
<p>Or, if you just want to push your patch queue:</p>
<pre class="eval">cd .hg/patches
hg commit -m "Some message"
hg push <a class=" external" href="ssh://hg.mozilla.org/users/your-hg_username.domain/my-repo1" rel="freelink">ssh://hg.mozilla.org/users/your-hg_u...omain/my-repo1</a>
</pre>
<p>In either case, you may also want to add that path to the repository's hgrc, so you don't have to type it every time. Put something like this in <code>.hg/hgrc</code>:</p>
<pre class="eval">[paths]
default-push = <a class=" external" href="ssh://hg.mozilla.org/users/your-hg_username.domain/my-repo1" rel="freelink">ssh://hg.mozilla.org/users/your-hg_u...omain/my-repo1</a>
</pre>
<h2>Pulling your changes</h2>
<p>You may wish to use this repository to share changes between machines. For this, start by doing the exact same setup on the other machine. In other words, if you have pulled mozilla-central from your first machine, pull it from the second machine. If you have created a queue on the first machine, create a queue on the second machine, etc.</p>
<p>Then, to pull the complete repo:</p>
<pre class="eval">hg pull <a class=" external" href="ssh://hg.mozilla.org/users/your-hg_username.domain/my-repo1" rel="freelink">ssh://hg.mozilla.org/users/your-hg_u...omain/my-repo1</a>
</pre>
<p>Or, to pull only the patch queue:</p>
<pre class="eval">cd .hg/patches
hg pull <a class=" external" href="ssh://hg.mozilla.org/users/your-hg_username.domain/my-repo1" rel="freelink">ssh://hg.mozilla.org/users/your-hg_u...omain/my-repo1</a>
</pre>
Revert to this revision