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

[John Pye]

Hi Christian,

I actually just asked a similar question to this list ('Multiple 
change-sources, multiple projects'). You've got the right list.

It occurs to me that if you ca set up the two views, then all the 
security stuff should be easy to implement using apache authentication 
and allow/deny rules. I'm not sure if these are possible in conjuction 
with the 'ProxyPassReverse' command that Brian Warner recommended, but 
it would be worth a try.

The other issue which I was a bit confused about was the use of the 
PBChangeSource() gizmo. This needs to listen on a single port, but it 
seems that you can set up multiple PBChangeSources for each buildmaster. 
But it seems that there is no way to say which PBChangeSource 
corresponds to which scheduler. Which means that a change in project X 
will cause the AnyBranchScheduler to query project Y for changes, which 
shouldn't really be necessary. Or am I wrong on that?

On the basis of this second problem, I was starting to think that 
multiple buildmasters would be required. Which then introduces the 
problem of the server being overloaded by attempts to build multiple 
projects at once; it wouldn't be so easy to put in place sensible 
queuing of builds when things are busy.

Please let us know how you go.

Cheers
JP

Christian Hudon wrote:
> 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
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting 
> language
> that extends applications into web and mobile media. Attend the live 
> webcast
> and join the prime developer group breaking into this new coding 
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
>


-- 
John Pye
Department of Mechanical and Manufacturing Engineering
University of New South Wales, Sydney, Australia
http://pye.dyndns.org/