Mercurial path with branch

30 views
Skip to first unread message

Jon Hodgson

unread,
Jan 22, 2012, 9:42:50 AM1/22/12
to Bitten
Hi,

Since I'm a Trac user Bitten looks like a potentially good solution to
my CI needs, however the documentation seems rather out of date, or at
least incomplete.

I'm using Mercurial.

Is it possible to set a build configuration to trigger a build when a
changeset is committed to a specific branch? If so then what is the
syntax for this?

Also will it respond to changes in subrepositories, or is there
perhaps a syntax to what for changes changes in those seperately
(actually the second is probably the more useful to me).

osimons

unread,
Sep 25, 2013, 5:22:21 PM9/25/13
to bit...@googlegroups.com, jonhodgso...@googlemail.com

On Sunday, January 22, 2012 3:42:50 PM UTC+1, Jon Hodgson wrote:
I'm using Mercurial.

Is it possible to set a build configuration to trigger a build when a
changeset is committed to a specific branch? If so then what is the
syntax for this?
 
No, sorry. DVCS branches are not yet supported, see:
http://bitten.edgewall.org/ticket/342#comment:22

Bitten supports multiple repositories and any repository connector that hooks into this model (like hg), but there is no code that can act on branches. Bitten only knows about "paths" in the repository.
 
Also will it respond to changes in subrepositories, or is there
perhaps a syntax to what for changes changes in those seperately
(actually the second is probably the more useful to me).

Subrepositories will be supported only if they are defined at the root of a default project, and thereby would look and act like any other Trac-attached repository in multi-repository model. Trac has no support for attaching repositories further down into the tree, and it won't go looking in subrepositories (nor svn:externals or similar).


:::simon

osimons

unread,
Sep 25, 2013, 5:32:26 PM9/25/13
to bit...@googlegroups.com, jonhodgso...@googlemail.com

Oops. Seems my news reader has jumbled my group RSS feed, and presented a 20 month topic as 'new' to me... The topic content seemed so fresh that I didn't really notice until after posting ;-)

Sorry for the noise - but happy about it if this can revive the discussion about what to do about branches that aren't based on repository paths.


:::simon

Reply all
Reply to author
Forward
0 new messages