Crucible

Developer creates a new branch.

Developer writes code and commits changes.

Developer creates a review in Crucible for the branch.

Reviewers inspect the code and add comments.

Developer addresses the comments and updates the code.

Once approved, the branch is merged into the main codebase.

Code is committed to the main repository.

Crucible automatically creates a review for the commit.

Reviewers inspect the changes and add comments.

Developer addresses the comments and creates a fix commit.

The fix commit is reviewed and merged.

Security-focused review is initiated.

Reviewers with security expertise inspect the code.

Vulnerabilities are identified and documented as comments.

Developer addresses the vulnerabilities.

Security review is re-run to ensure fixes are adequate.

Audit review is initiated.

Reviewers verify code against compliance requirements.

Non-compliant sections are identified and documented.

Developer updates the code to meet compliance standards.

Audit review is re-run to confirm compliance.

Experienced developer writes code.

A review is created to share the code with less experienced developers.

Reviewers inspect the code and ask questions.

The experienced developer answers the questions and provides explanations.

Knowledge is transferred to the team.

Senior developer selects key areas of the codebase.

Review is initiated involving the new team member.

Senior developer walks the new member through the code.

New member asks questions and gains understanding.

The review serves as documentation and training.