[Buildbot-devel] Buildbot fetching wrong revisions? [Bzr]

[Marcus Lindblom]

On 2010-01-05 13:48, Sudharshan S wrote:
> Hi all,
> We have this following setup to test some code, say Spam and Eggs who
> are housed in different repositories. The current setup is something
> like,
>
> 1.) A single buildmaster
> 2.) Two buildslaves Spam_slave, Egg_slave each for Spam and Egg
> 3.) Two builders Spam_builder, Egg_builder
> 4.) Two schedulers Spam_scheduler, Egg_scheduler
>
> It should be noted that the two repositories do not have anything in
> common. I had written the master.cfg in such a way that it reads
> certain settings from a config file (mostly workdir, slave_password,
> slave_user) .. etc and completes 2, 3 and 4 listed above.
>
> I am also using the BzrPoller script to poll the Bzr repositories once
> in a while. Picked it up from trac and modified it a bit to suit my
> needs.
>
> The problem is, buildbot is always trying to fetch the latest revision
> among the two repositores.
> For eg, if Spam is at rev 120, and Egg is at 30. The Egg_slave is
> trying to fetch revision 120. I can confirm that I create BzrPoller
> objects separately for the two projects.
>
> I have a feeling in sources.py, the code to get the latest revision
> (where it does bzr version-info) is getting executed from the wrong
> directory.
>
> Any comments? Is there something I should look at?

BuildBot doesn't support running two different repositories on one 
master. (You can hack it with SVN and maybe some other, but not for Bzr 
and similar)

It's a big limitation (that wasn't that bad until all DVCS:es came 
along) that we'll certainly address in the future.

The workaround is to run two master processes on the server. (We run 5 
buildmasters then some simple javascript/jquery to merge the grid views 
onto a single page.)

Cheers,
/Marcus