[Buildbot-devel] Multiple SVN repositories

Joel Becker Joel.Becker at oracle.com
Fri Nov 11 06:08:36 UTC 2005

	First off, I have to say that Buildbot is quite nice to set up
and use.  I'm glad I stumbled across it!
	I've a simple problem.  It doesn't look like a single
buildmaster can handle multiple repositories.  I'm using Subversion, and like many, many Subversion users, we use one repository per project instead of a huge repository with many modules (ala CVS).
	But PBChangeSource does not have a way to specify the
repository.  So each of my AnyBranchSchedulers sees a change as relevant
to its own repository.  This results in any change to any repository
causing a build in _all_ repositories.
	Now, the naive solution is a buildmaster per repository.  Then a
matching buildslave per repository.  This gets out of control quick.
For example, on a big build box I have chroots for 4 major
distributions.  In each chroot, I run a buildslave.  Now, instead, I
have to run a buildslave per repository.  With four repositories, my
build box is now running 16 buildslave processes.  Not to mention
needing four different slave ports on the master.  And we have more than
four repositories.
	If I could map repository->pbchange->scheduler, I only need the
one builder.  Is there any chance such a functionality could be



"Reality is merely an illusion, albeit a very persistent one."
        - Albert Einstien

Joel Becker
Principal Software Developer
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

More information about the devel mailing list