Setting up Tarmac

John Arbash Meinel john at arbash-meinel.com
Fri Sep 2 13:45:44 UTC 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So I played around with a dummy Tarmac installation on Canonistack. I
set it up to merge proposals for a dummy branch of Meliae. It didn't
seem particularly hard to set up. There are a couple of rough edges, but
overall I think it works pretty well.

It is nice that it puts the failure results back on the Launchpad page.
Though with our "failures generate the entire success + failure log to
stdout/stderr" that may be a bit much to put on a Launchpad post.

You can sort of see what I mean here:
  https://code.launchpad.net/~jameinel/meliae/bad_test/+merge/73807

So I don't think it is ready to be a replacement for PQM just yet. We'll
have to change how bzr generates its failure logs first. (By default
tarmac just reads all of stderr and prints it out.)

Also, Tarmac doesn't have the visibility of the current run that PQM
has. At least as near as I can tell, there isn't a web UI that would let
you see how many patches are in the queue and when your patch is going
to get merged, etc.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5g3ggACgkQJdeBCYSNAAOHbQCcC6Q8rJUW2MaaI9OoqFkSl+pi
7d0AoJfMI+IKOv7BCRaExv1b/PgGxh4P
=79lD
-----END PGP SIGNATURE-----



More information about the bazaar mailing list