81 

    82 Full .hg/hgrc example for contributors having ssh access to ``hg.logilab.org`` :

    83 

    84     [paths]

    85     default = https://hg.logilab.org/master/cubicweb

    86     default-push = ssh://hg@hg.logilab.org/review/cubicweb

    87 

    88     [email]

    89     to = cubicweb-devel@lists.cubicweb.org

    90 

    91     [patchbomb]

    92     publicurl = https://hg.logilab.org/review/cubicweb

    93     flagtemplate = "{separate(' ', 'cubicweb', flags)}"

    94 

    95     [jenkins]

    96     url = https://jenkins.logilab.org/

    97     job = cubicweb-default

    98 

    99 If you don't have ssh access to ``hg.logilab.org``, you can use your own Mercurial server and

   100 change ``default-push`` and ``publicurl`` accordingly.

   101 A list of services that provides hosting of Mercurial repositories is available

   102 on https://www.mercurial-scm.org/wiki/MercurialHosting.

   103 

   104 * ``hg pull`` will pull on master repo (public changesets).

   105 * ``hg push`` will push on review repo using ssh.

   106 * When sending an email to the list, it will add a "Available at" with command

   107   to pull the draft series on the public repo.

   108 * Using https://hg.logilab.org/master/logilab/devtools/file/tip/hgext/jenkins.py

   109   mercurial extension, ``hg show jenkins`` display jenkins build status for

   110   each changeset. Read https://www.mercurial-scm.org/wiki/UsingExtensions to learn how

   111   to enable a new extension in mercurial.