Last updated November 07, 2012 19:14, by nvause

» Project Kenai Documentation and Training    » How Do I ...    » Source Code Management

Using Mercurial on Microsoft Windows Systems

Once you have a Mercurial client installed on your local system, you can check out code and check it back into your project repository. The following instructions for command-line Mercurial should get you started. For full instructions on using Mercurial, see

Because of the better security and better handling of large files, it's best to use the SSH protocol to check files into your project repository. This page assumes you have set up an SSH key and you've configured Mercurial to use plink to manage the key, as described on the following two pages:

  1. To initially set up your repository, you need to know the name of the project and the name of the source repository. For example, for a project named bluebird with a Mercurial repository named bluebird~mercurial-code-repository, the default read-write URL would be:
  2. Change directories on your local machine to the directory in which you want your new hg repository directory to be created, then do the initial clone and create. For example:
     > cd \myproj
     > hg clone ssh:// bluebird-hg
    Note: If the command hangs when you're using Mercurial with PuTTY's Plink command-line interface, Plink is likely to be waiting for you to confirm the Host SSH key signature, which you can't do directly at this point. What you can do is start PuTTY, then in the Session settings enter the Host Name part of the URL (for example, ssh:// and click Open, and then type Y to save the host SSH key in the registry. You should then see the command complete in the Command window.
  3. Change directories to the new directory:
     > cd bluebird-hg
  4. Copy a file to the local working copy and then add it in Mercurial.
     > cp \myjavafiles\
     > hg add
  5. Commit the file to the local repository.
     > hg commit -m"First commit to bluebird repository"
  6. Pull any changes from the server repository:
     > hg pull
  7. Update the local working copy:
     > hg update
  8. Check the file into your project repository on the server:
     > hg push
  9. You see the a series of messages similar to the following:
     pushing to ssh://
     searching for changes
     remote: adding changesets
     remote: adding manifests
     remote: adding file changes
     remote: added 1 changesets with 1 changes to 1 files

You now have a file in your repository.

Project Features

Wiki Controls

About this Project

Help for Site Tools was started in November 2009, is owned by kenaiadmin, and has 64 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20160708.bf2ac18). © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
Please Confirm