User:Minooz/Mercurial

Mercurial Project

Mercurial

Main website @ http://mercurial.selenic.com/

Mozilla Mercurial @ https://wiki.mozilla.org/Mercurial_on_Windows

compare version controls [1]

Understanding Mercurial @ http://mercurial.selenic.com/wiki/UnderstandingMercurial

Tutorial-wiki @ http://mercurial.selenic.com/wiki/Tutorial

Installation

Installing in windows[2]

More about installation [3]

Mercurial on Eclipse

Eclipse-Mercurial [4]

Eclipse-Mercurial Video [5]-Demo

Documentation for Eclipse-Mercurial [6]

Documentation

The Definitive Guide, is a documentation for hg (PDF or Html).

TortoiseHg Documentation [7]

Creating a Version Control Repository [8]

Mozilla Mercurial [9]

• Some Basic Terms (from The Definitive Guide)

1- The .hg directory is the “real” repository, and all of the files and directories that coexist with it are said to live in the working directory.

An easy way to remember the distinction is that the repository contains the history of your project, while the working directory contains a snapshot of your project at a particular point in history.

2- The hg log command gives us a view of the history of changes in the repository. By default, this command prints a brief paragraph of output for each change to the project that was recorded.

Each of these recorded events are called a changeset, because it can contain a record of changes to several files. Changeset is also referred to aschange, cset, revision or rev.

3- Changeset field has the format of a number (identifier, which is only valid in that repository) followed by a colon, followed by a hexadecimal (or hex) string. These are identifiers for the changeset.

The hex string is a unique identifier: the same hex string will always refer to the same changeset in every copy of this repository. The number is shorter and easier to type than the hex string, but it isn't unique: the same number in two different clones of a repository may identify different changesets. changeset: 0:0a04b987be5a

4- Mercurial uses revision numbers purely as a convenient shorthand. If you need to discuss a changeset with someone, or make a record of a changeset for some other reason (for example, in a bug report), use the hexadecimal identifier.

5- Some changesets, have a tag field. A tag is another way to identify a changeset, by giving it an easy-to-remember name. tag: tip

6- To get the changeset id of the tipmost changeset of a remote repository you can do: When it changes, you have new changesets in the remote repository.[10]

> hg id -i -r tip http://www.selenic.com/repo/hello 
[[[link-to-a-page]]]
[url=http://example.com]Example[/url]
82e55d328c8c

7- Some aliases:

st = status / ci = commit /

8- mq tutorial [11]

9- ant task for hg ANT4HG

Challenges

• 1- First challenge is how to trim history of a repository.

We have a Mercurial repository called A. We want to clone repo A and create a new repo called B.

It's possible to use 'init' and create a new repo and just copy the files from repo A and add them.

This way the revision number will reset. And we will start repo B from the tip of the repo A.

The problem appears if we want to clone just the tip of the repo A and keep the same revision number of the 'tip'.

Here are some links that we went through, but no success yet.

Trimming History

.hgrc file

mq strip changeset

Editing History!!

Continuous Integration System

• Hudosn

http://hudson-ci.org/

• Apache Continuum

http://continuum.apache.org/

• Cruise Control

http://cruisecontrol.sourceforge.net/

http://cruisecontrol.sourceforge.net/dashboard.html

Pragmatic Project Automation

Pragmatic Bookshelf

• Maven

• Buildbot

The Buildbot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. [12]

Here is the documentation for Buildbot. This video also explains different features of this system.

The buildmaster is usually fed Changes by some sort of version control system, which may cause builds to be run. As the builds are performed, various status messages are produced, which are then sent to any registered Status Targets.

-Change Sources, which create a Change object each time something is modified in the VC repository. Most ChangeSources listen for messages from a hook script of some sort. Some sources actively poll the repository on a regular basis. All Changes are fed to the Schedulers.

- Schedulers, which decide when builds should be performed. They collect Changes into BuildRequests, which are then queued for delivery to Builders until a buildslave is available.

-Builders, which control exactly how each build is performed (with a series of BuildSteps, configured in a BuildFactory). Each Build is run on a single buildslave.

-Status plugins, which deliver information about the build results through protocols like HTTP, mail, and IRC.

• Common Requirements

At a bare minimum, you'll need the following for both the buildmaster and a buildslave:

-Python: http://www.python.org Buildbot requires python-2.4 or later.

-Twisted: http://twistedmatrix.com (Twisted is an event-driven networking engine written in Python and licensed under the MIT license.)

Requirements for Buildmaster

-sqlite3: http://pypi.python.org/pypi/pysqlite

The sqlite3 package is required for python-2.5 and earlier (it is already included in python-2.5 and later, but the version in python-2.5 has nasty bugs)

-simplejson: http://pypi.python.org/pypi/simplejson

The simplejson package is required for python-2.5 and earlier (it is already included as json in python-2.6 and later)

-Jinja2: http://jinja.pocoo.org/2

Jinja2 is a general purpose templating language and is used by Buildbot to generate the HTML output.