best way to synchronize mq patches from a master repo as mq patches to a set of mercurial clones

[Greg Ward]

On Tue, Apr 13, 2010 at 7:09 AM, Dorin Ioan Marinca
<dorin.marinca at gmail.com> wrote:
> I have to run a dozen of different build tests on a code base maintained in
> a mercurial repository. I don't want to run serially these tests on same
> repository because they modify a set of common files and I want to run them
> in parallel on different machines. Also, after all tests are run I want to
> have access to latest test results from those test work areas. Currently I'm
> cloning the master repository a dozen of times and run in each clone one
> different test. Before each test execution I do a pull/update/purge
> preparation sequence in order to start the test on latest clean state.
> That's good for me.

This is not really a version-control question, it's a build question.
I think you need to look at a continuous integration server like
BuildBot.  It has a lot of really nice features that are designed for
just what you are trying to do.

> I'm also preparing new changes using mq extension that I would test on all
> clones as above before committing them. For testing some ready candidate mq
> patches I want somehow to deploy/synchronize them to be available in test
> clones and apply those ready for testing using some guard before running the
> test.

...for example, BuildBot has a "try" feature that lets you send it a
patch to try out before you actually commit it.  It checks out the
latest "official" version, applies your patch, and runs your
build/test script(s).  If you've set things up appropriately, it will
do this on multiple build slaves concurrently.  Very fun.

http://buildbot.net/trac

(There are other continuous integration servers in the world, but only
one I'm familiar with is BuildBot.)

Greg