Software store>Development tools>Code quality management> Crucible- code review tool

Commodity code:S20151109153919771

Crucible- code review tool

Help you submit a higher quality code!

Before 31 December, the purchase of 250-500 users donated 4 hours online installation support, and more than 2000 users with 2 days on-site technical support (excluding travel)

Commodity details Help document Purchase support Technical community
Peer collaborative code review

Code review = high quality code.

Through the Crucible code review workflow, you can easily review the code, discuss changes, share knowledge, and find defects.

Crucible for your Subversion, CVS, Perforce code review more easily and efficiently.


Authorization mode:
A Crucible business license includes:
1 a single Crucible instance is deployed on a server in a production environment;
2 create unlimited number of projects and issues;
3 permanent use Crucible;
12 provide 4 months of software technical support services - including new version updates and email support (in English);
5 provide all source code.
For more information, please refer toEND USER AGREEMENT ATLASSIAN (end user license agreement).
What is the number of users:
User number is the number of users who have access to the application in the application. The number of users here is the number of registered users who have access rights to the application, and not the number of concurrent users (User Concurrent). If the application is open to an anonymous user, an anonymous user is not counted.


Flexible code review

Pre error review

JIRA integration

Code quality

Notification & Report

Full screen view



The flexible code review

Crucible provides a variety of ways to submit code review before and after:
1 code review based on Workflow
2 a quick review of the code segment by cutting
3 create a review by the command line
4 a key to review the changes set and related issues

The nested comment system
Point, click, comment. Crucible can be any review of the results into a nested comment form, easy to capture major defects, improve the code structure, and discuss the urgent need to improve.
The integration of JIRA

The code review is integrated into your daily development process:
1 view and code review results related to the source code
2 view and create code review from JIRA
3 Crucible code review results into the executable JIRA problem

The iterative review
Code review is essentially an iterative, review and comment on the code, as well as the results of the review, the Crucible can track the documents that have been covered, and then re set them into a new review results added to the report.
The distributed team

Crucible bridging the gap between distributed teams makes code review possible
1 through email and RSS for real-time feedback
2 review the detailed records of all review activities
3 active flow including source code and code review


Flexible code review

The lightweight technology, formal code reviews

Crucible provides configuration options to track and complete review:
1 define workflow
2 review and supervision
3 one or more participants

The site code is discussed

Crucible supports the full built-in discussion model, so that the team can be different in different time to discuss the code.
Open a comment on a specific source code line, file, or the entire review process.
Tag the comment tag as a defect, add a custom class, or create a JIRA problem from the review of any of the notes.

The update is never out of date

The reviewer can review the different versions of the same issue under the revised opinion. If a newer version of the revised version appears, Crucible will mark the file as obsolete, or provide a quick way to add it to the latest version.


Submitted before review

Support review before submission
Review the code before submitting it to keep the code quality and make sure that any code is reviewed at the time of the input.
By creating a command line review
When you are in the programming, you can quickly pass the command line to the code before the review, without the need to log in Crucible, it will not change the context.
The iterative review before submission

In the process of submission of the review process, the code can be reconstructed, changed and upgraded. Crucible is very focused on this, and you can make sure that you can easily update them in the review.

The particular piece of code review

Some source code (or text) needs to be discussed in the context of an informal review, and Crucible provides several ways to allow you to discuss code in an informal way:
1 code review - in the team, just a simple paste code and text can begin to discuss
2 to change the collection - for the information submitted, Crucible provides a very free form of comment


JIRA integration

We bring the high quality code for JIRA

The combination of JIRA and Crucible code review:
1 browse the code review related to the project.
2 monitor code review activities on the JIRA control panel
3 create code review directly on JIRA
4 based on the review of the activities of the automatic upgrade JIRA release status

The JIRA in Crucible visualization

Use Crucible to minimize the context of the change to get the code review related issues:
1 review and review the relevant Crucible code review
2 in Crucible as long as the mouse slip to the JIRA key words to visit all the relevant details

It will be released into the notes
The development team can improve the code quality, as well as to save working hours by transforming the important Crucible review notes into a JIRA release that can be easily tracked.
The transformation from Crucible JIRA
The transformation and the results of the review of Crucible related issue, workflow, no need to transfer to and fro you or, even better, directly adding a trigger for your JIRA workflow, can automatically update the release state based on the review of the activities.
The JIRA workflow
In some cases, the code review is a mandatory part of the development workflow, and in Crucible, the open review and review of the changes in the collection can be customized to end the JIRA workflow.
Code quality
The traceability

Crucible provides a view to directly view source code quality:
1 to understand the source code associated with the JIRA release
2 developers can display their code comments and review activities through a unified view.
3 use FishEye to review the relevant source code review history

We share the best practices

Review code is also learning code
1 to guide their programming skills by inviting new developers to code reviews.
2 create a filter for the new team member to submit the code to maintain real-time updates
3 provide a new way of working with experienced developers to develop their ideas

The scope of the review
Do you want to know how your review process is conducted? Which change collection is being reviewed? Which version of the revised version has not been considered? How much code is being reviewed? So many problems! The scope of the review report will tell you all the answers. Easy to see which part of the code base needs to strengthen the review.
Notification and report
I notice

To fully grasp the situation of your review, you can:
1 review activities via email and RSS, including new reviews, status updates, or file attachments.
2 to set up a bookmark or mark the most favorite comments to view them later.

The review reminder
Sometimes developers will forget the code review of this activity, you can automatically or manually to remind those who did not complete the review of the review, according to the date set to remind, or manually use the window to remind them of the vibration function.
The control panel and report

Crucible offers a variety of features to help your team keep their workload:
1 in your inbox, you will receive a review of what code to complete or which code is being reviewed by others.
2 active flow shows the latest comments from the entire project or sample.
3 window to stop the report and process can help you quickly browse who may hinder the review of the work or what the current state.

I accept the review
Crucible holds all of the code review details, dates back to the history of a specific code review. For the development team to do things to maintain a complete review of the process, if you use JIRA and FishEye, you can view the release, comment and source code.
We share and use @ remind others

At the right time to invite the right person to carry out the code discussion, the team member is invited to be invited to the discussion group and share the results of the review.

Full screen view
The nested comments
Nested comments on source code with your peers
The simple review and comment
Simply click on the source code line to add comments
We review the content

Review the contents of the collection, search files, or upload a patch to easily add review

The code review
Only the title and code can begin code review
The change set is discussed
The use of code change set notes for discussion
The formal code reviews
By title, reviewers and objects to begin a formal code review, you can link to the review in the relevant JIRA release
The activity flow
In active flow, it is easy to confirm that all of the recent code reviews.
The Crucible inbox

Comprehensive control of code review by the inbox

The list of code quality inspection

Using Crucible and FishEye, you can easily determine how many of your items have been or not reviewed.


If you have a problem, please call me.010-57410251, or online consulting service QQ Click here to send a message to me.

Publication consultation:

Consulting reply time is 9:00-18:00, please be patient and wait for the reply. If you have a problem, please call me.010-57410251.

Consultation content:
Total0A topic discussionPublish a topic