This document describes several forms of Crucible Workflow in detail. Depending on the size of your team, there are four different ways that a development team could use Crucible for code reviews. Choose the workflow which suits your team.
- Author commits new work.
- Author creates the review, and adds comments using the easy web interface.
- Author summarizes and closes the review, saving the code comments in Crucible's database, which is stored outside the repository.
Diagram: Workflow for Lightweight Code Commenting
One-to-One Reviews (Agile Pair)
- Author creates the review.
- Author invites reviewer to take part in the review.
- Reviewer creates comments on the code.
- Author responds to reviewer comments.
- Follow-up comments are made if necessary.
- Reviewer finishes own review process.
- Author summarizes and closes the review.
Diagram: Workflow for One-to-One Reviews
For more information on one-to-one reviews, see The Crucible workflow. The workflow process in Crucible is covered in detail within this document.
One-to-Many Reviews Without a Moderator (Agile Team)
- Author creates the review.
- Author invites reviewers to take part in the review.
- Reviewers make comments on the code.
- Author responds to reviewer comments, follow-up comments are made if necessary.
- Reviewers complete their reviews.
- Author summarizes and closes the review.
Diagram: Workflow for One-to-Many Reviews
- Author creates the review.
- Moderator invites reviewers to take part in the review.
- Reviewers make comments on the code.
- Author responds to reviewer comments.
- Follow-up comments are made if necessary.
- Each discussion point is settled by the Moderator.
- Moderator summarizes and closes the review.
Diagram: Workflow for Formal Group Reviews
To see a simple example of how to use Crucible with two people, see The Crucible workflow.