Currently Buildbot does not support multiple repositories. If one desires to have this then separate instances of Buildbot need to be run.
Still I'm curious if anyone has come up with a creative workaround to get this feature working anyway.
Currently Buildbot does not support multiple repositories. If one desires to have this then separate instances of Buildbot need to be run.
Still I'm curious if anyone has come up with a creative workaround to get this feature working anyway.
|> Currently Buildbot does not support multiple repositories.
I don't really understand the question.. sorry. Do you mean that you have to run multiple master servers? It is actually advised by the buildbot devs to do so, but the contrary works for me: you can have in the same master.cfg
multiple slaves (columns in the waterfall) and for each or them a BuildFactory
with different first steps of the type: Git(repourl=...)
and/or Mercurial(repourl=...)
etc.
Each will clone/pull from different repositories and you can even add some more checkouts that are needed in subsequent steps (using maven or directly your scm client). The only issue with having a unique master.cfg
file is that all builders will have only one method for getting notifications of changes; we have for example PBChangeSource()
(master is notified by remote code, it has nothing to do). If for instance you have an SCM with good PBChangeSource support (e.g., svn, hg, git) and an other ones with bad support (e.g., MKS) then you should have two master server instances in order to cope with that.
Hope it'll help.
Cheers,
Christophe.
= Every generalization is false, including this one. --Mark Twain =
BuildBot now supports multiple repositories, as of 0.8.x. :)
Enjoy! :)