Re: Best practices for supporting multiple projects with a RB installation
Hi Keith, Right now, default reviewers are global across repositories. This will be optionally per-repository in 1.1, though. In our case, most of our repositories are actually just branches off the same main repository anyway, and different trees in that branch should only be developed on certain repositories, so it sorta works out. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.review-board.org VMware, Inc. - http://www.vmware.com On Tue, Sep 1, 2009 at 1:08 PM, Keith wrote: > > How do you specify the default reviewer regular expressions given that > many source repositories? Examples would be great. > > Thanks in advance, > > Keith > > On Aug 20, 4:34 pm, Christian Hammond wrote: > > Hi, > > > > At VMware, we have two Review Board servers, one for engineers and one > for > > QA contractors that otherwise don't have access to the main repositories. > > > > The main Review Board server hosts all the groups and repositories for > main > > engineering. As of right now, there are 217 groups (generally one per > > team/project) across 22 repositories. We've found that this works quite > > well, and is actually ideal for when you have a change that should be > looked > > at by a few different groups. > > > > Christian > > > > -- > > Christian Hammond - chip...@chipx86.com > > Review Board -http://www.review-board.org > > VMware, Inc. -http://www.vmware.com > > > > On Thu, Aug 20, 2009 at 8:11 AM, Thilo-Alexander Ginkel < > th...@ginkel.com>wrote: > > > > > > > > > > > > > Hello everybody, > > > > > I was wondering whether there are any best practices or experiences on > how > > > to > > > support multiple projects (within the same organization) with a Review > > > Board > > > installation (the developers working on each project are typically > > > different > > > people). > > > > > Would you try to fit everything into the same site or rather install a > RB > > > site > > > for each project? > > > > > Thanks, > > > Thilo > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "reviewboard" group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: Best practices for supporting multiple projects with a RB installation
How do you specify the default reviewer regular expressions given that many source repositories? Examples would be great. Thanks in advance, Keith On Aug 20, 4:34 pm, Christian Hammond wrote: > Hi, > > At VMware, we have two Review Board servers, one for engineers and one for > QA contractors that otherwise don't have access to the main repositories. > > The main Review Board server hosts all the groups and repositories for main > engineering. As of right now, there are 217 groups (generally one per > team/project) across 22 repositories. We've found that this works quite > well, and is actually ideal for when you have a change that should be looked > at by a few different groups. > > Christian > > -- > Christian Hammond - chip...@chipx86.com > Review Board -http://www.review-board.org > VMware, Inc. -http://www.vmware.com > > On Thu, Aug 20, 2009 at 8:11 AM, Thilo-Alexander Ginkel > wrote: > > > > > > > Hello everybody, > > > I was wondering whether there are any best practices or experiences on how > > to > > support multiple projects (within the same organization) with a Review > > Board > > installation (the developers working on each project are typically > > different > > people). > > > Would you try to fit everything into the same site or rather install a RB > > site > > for each project? > > > Thanks, > > Thilo --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "reviewboard" group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
Re: Best practices for supporting multiple projects with a RB installation
Hi, At VMware, we have two Review Board servers, one for engineers and one for QA contractors that otherwise don't have access to the main repositories. The main Review Board server hosts all the groups and repositories for main engineering. As of right now, there are 217 groups (generally one per team/project) across 22 repositories. We've found that this works quite well, and is actually ideal for when you have a change that should be looked at by a few different groups. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.review-board.org VMware, Inc. - http://www.vmware.com On Thu, Aug 20, 2009 at 8:11 AM, Thilo-Alexander Ginkel wrote: > > Hello everybody, > > I was wondering whether there are any best practices or experiences on how > to > support multiple projects (within the same organization) with a Review > Board > installation (the developers working on each project are typically > different > people). > > Would you try to fit everything into the same site or rather install a RB > site > for each project? > > Thanks, > Thilo > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "reviewboard" group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~--~~~~--~~--~--~---
