Child pages
  • Crew Review Board
Skip to end of metadata
Go to start of metadata

Problem

  1. For people who go on co-op on far away lands, there is no reliable way to collaborate with those currently in school.
  2. We need pair programming (yay!).

Solution

We are going to setup a Review Board (tm) instance.
Here is our instance.

Settings and Setting up

In the Admin page, go to Database -> Tools -> Add tool

Name

Class name

git

scmtools.git.GitTool

To add a repository, the server needs to have a local (working) copy of the git repository. This should be kept up-to-date (which can be done with a post-receive script (Not implemented)).

Adding a Repository

Example:

Name

DDS Backend

Path

/blah/blah/backend/.git

Mirror Path

git@crew-git.ccs.neu.edu:backend.git

Repository Type

git

The "Mirror Path" is required because the post-review tool will send the origin gir-url which is used to match the repository.

LDAP settings

LDAP Server

ldap://cluster.ldap.ccs.neu.edu

LDAP Base DN

ou=people,dc=ccs,dc=neu,dc=edu

E-Mail LDAP Attribute

mail

User Mask

(uid=%s)

post-review

A copy of post-review is at /proj/crew/lee/bin/post-review (adjusted with settings).

Using post-review

  1. Write some code.
  2. git commit (but do not push)
  3. post-review (from the directory)
  4. follow the link, publish (remember the review number)
  5. other people review your code, make changes
  6. post-review -r <review number>
  7. and so on, until rock solid.
  • No labels