How to integrate Jira, fisheye, and crucible for codereview

I believe that Atlassian is familiar to everyone. I Know That confluence has wood and Jira wood. Although these products are charged, I can apply for a free license for schools and open-source organizations, you can also apply for a trial.

 

Some time ago, in order to facilitate codereview, I tried the combination of fisheye + crucible, and fisheye can be conveniently viewed.CodeCrucible is a powerful tool for codereview. Because they belong to the same Atlassian, they can be integrated with Jira, manage the project issue in Jira, and associate code changes and codereview Based on the ID.

1. System Configuration

There is not much to say about how to build these systems. There are a lot of online tutorials. fisheye + Crucible has integrated installation packages that can be run independently. Jira needs to be installed separately. We recommend that you use the standalone installation package on the official website of Atlassian. If you select the war/ear method,Multiple products cannot be installed in the same Tomcat . The installation method I selected is as follows:

• Fisheye + crucible 2.4.3 integrate an independent installation package, such as http://digitalsonic.net: 8060
• JIRA 4.2 is deployed in a tomcat container, such as a http://digitalsonic.net (limited resources, Hudson and sonar are also deployed on This tomcat)
• All databases are stored in MySQL (the default database solution is not applicable to formal scenarios)

1.1 Jira Configuration

In the fisheye configuration in Jira administration, configure the address http://digitalsonic.net for Fisheye: 8060, enable wiki render and crucible integration; in "repository mappings", configure the fising between the fisheye code base and the Jira project so that you can jump between the two. Finally, configure trusted applications in "trusted applications ".ProgramAnd fill in the fisheye address as instructed.

 

Enable "sub-tasks" in "global settings" and "Accept Remote api cils" and "allow unassigned issues" in "general configuration ".

1.2 configuration of fisheye and crucible Terminals

Go to the "adminstration" interface, add a new link in "application links", and enter the Jira address as prompted.

Fisheye is recommended to use the new version. It is said that the old version has some problems in indexing the code base, and the Occupied storage space will be relatively large. 2. Start Review

Before getting started, of course, we need to create corresponding projects in Jira and fisheye. Several key roles must have their own accounts on these systems. On fisheye, You can initialize and scan the code library first, so that even if you do not do codereview, it is good to see the code.

 

Create a codereview in two ways:

1. Click "create Review" on the Crucible interface"
2. On an issue page of Jira, go to the "Source" tab and click "create crucible Review" (the advantage is that codereview can be created directly for all the code changed by an issue)

If you select the former option, you need to select the project and codereview content in the subsequent dialog box. Here are several methods. We recommend that you select the first three options-browse changesets) view the code library (javase repositories) and find files. I use a lot of browsing Change sets, and select the codereview range based on the code library, branches, and other content.

 

Click "done" to edit the details of this review. Select author and reviewers to be the same person, but you 'd better not review yourself, in the Edit review detail interface, you can also associate issue, set the target, set the validity period, and so on.

 

After review is started, you can select the changed file on the left to view the change content. Click the code to add the review description to enter the text. Each reviewer can perform review independently to complete its own work. You just need to perform "complete" on your own.

 

After all users have completed their respective reviews, they can summarize and close this review. Click "summarize" and enter the summary. If you confirm that there are no comments to be added, simply "close review". Otherwise, "continue without close" will be performed ". Like Jira, reopen can also be performed after reivew is disabled.

 

It is recommended that the user names of the same person in several systems be consistent and can be consistent with the user names in SVN, so that it is more convenient to view. In addition, in order to associate SVN changes with the issue in Jira,Enter the issue ID in the comment when submitting the code.Otherwise, the connection fails.

 

 

Reference:

1. Integrating Jira with fisheye
2. JIRA integration in fisheye
3. Crucible User's Guide

(Pay attention to the software version used when viewing the official documentation)

 

Glossary:

 

JIRA-Excellent defect (Bug) tracking management software ( Issue tracker);
Confluence-Professional (Wiki) enterprise knowledge management and collaboration software;
Bamboo-Continuous integration of build server software ( Build Server);
Crowd-Single Sign-On authentication ( SSO) Application software;
Clover-Powerful and highly-configurable code coverage Analysis Tool ( Test with confidence);
Crucible-Effective code review tools ( Efficient code review);
Fisheye-Source codeDeep View tool ( Source code repository insight).

JIRAOnline Demo: Http://www.fangwai.net: 8080/
ConfluenceOnline Demo: Http://www.fangwai.net: 8081/
Online demonstration of fisheye + Crucible: Http://www.fangwai.net: 8060/

 

 

 

From:

Http://digitalsonic.iteye.com/blog/1095060