[Buildbot-devel] Mercurial and Categories

Benoît Allard benoit at aeteurope.nl
Fri Feb 26 08:45:38 UTC 2010

Charles-Henri d'Adhémar wrote:
> Hello everybody !
> I would like to use the "category" feature to use one single instance
> of buildbot for handling several distinct projects.
> I have not found out yet if it is possible to set a category attribute
> through buildbot's mercurial hooks.

About the background: the category property is not meant for this 
purpose, but more to distinguish the diffrent types of bots inside a 
same project, the example used in the doc is "test", the metabuildbot 
uses three categories: "doc", "full", and "generic". Buildbot is not 
meant **yet** to handle more project inside a same master.

We had this discussion earlier this week on how to integrate a "project" 
property, or a "repository" property. To quickly summarize, We settled 
on the idea that the ChangeSource has to give more information about the 
repository where does the change itself is originating. As this 
information already exists (the physical place where the change is), 
this would not need any configuration, in the contrary of the "category" 
feature. Then you should be able to fire a scheduler or the other 
depending on the value of this "repository" property as they will be 
different for all of your project repositories or sub-project repositories.

My understanding is that this feature should make it really soon into 
djmitche master branch as I provided a patch that almost does it. The 
remaining job is to rebase it onto warner's schedulerdb patches.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6031 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://buildbot.net/pipermail/devel/attachments/20100226/e413a745/attachment.bin>

More information about the devel mailing list