This is the documentation for Crucible 3.7. View the latest version of

Unknown macro: {spacejump}

or visit the latest Crucible documentation home page.

Atlassian Crucible is the on-premises code review solution for enterprise teams. It allows your development teams to catch major defects, improve code architecture, and discuss desired improvements, without the need for meetings.

This page provides an overview of how to use Crucible.

1. Point Crucible to your repositories

Crucible is all about code reviews. It's no surprise then that Crucible needs access to your source code.

A Crucible administrator can connect a repository managed by any of these tools:

2. Set up a Crucible project

A Crucible project allows you to

  • define default moderators, authors and reviewers for the reviews in that project.
  • define which people are eligible to be reviewers for the reviews in that project.
  • use permission schemes to restrict who can perform particular actions (e.g. 'Create Review') in that project.

A Crucible administrator can create new projects – see Creating a project.

3. Review something!

When you create a review you'll want to:

  • Add the files, changesets or other content that you want to be reviewed.
  • Choose the people who you want to be reviewers.

We've found that reviews should be created with care to get the best value from them:

  • Avoid overloading the review. Reviews should be focussed on just a few necessary files.
  • Avoid overcrowding the review. Reviewers should be selected with care, and should be guided individually on what to look for.

See Creating a review for more information.

 

 

 

 

 

 Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.