[Buildbot-devel] How to set up buildbot for two code bases with different access?

[Christian Hudon]

Hi,

I guess this would belong more on a buildbot-users mailing-list, but I 
couldn't find one... I'm working on setting up a buildbot where I work, 
but the setup is a bit complicated... I'd be really happy if someone 
whose knowledge of buildbot is better than mine could give some advice.

We have an opensource library, on which we work together with other 
people from outside the company. We also have proprietary in-house code, 
which depends on the library. Each of these is in its own subversion 
repository. I'd like to set up a buildbot for both of these code bases. 
I'd want the open-source builds to be visible to everyone, but the 
builds for the in-house stuff only visible to people inside the company. 
I'd also want a (successful) build of the open-source library to trigger 
a build of the in-house code

 From looking around the buildbot documentation, there would be two ways 
of approaching this:

1. Have everything run under one buildmaster, and use the categories 
features of the various status targets to create two views, one with 
everything and one with only the open-source stuff. My worry here is, 
would that setup be secure -- i.e. might people accessing the 
open-source waterfall view, say, be able with some url editing to view 
the build results for the in-house stuff too?

2. Have two buildmasters. This would be more of a known quantity 
security-wise. But here I'm not sure how to have the in-house 
buildmaster know about the changes and build results from the 
open-source one. Is that kind of thing, like say a 
RemoteBuildMasterChangeShource, supported?

Insigh would be much appreciated.

Thanks in advance,

  Christian