Crucible Connection

This section describes Crucible Connection.

What's Crucible Connection?

The AccuRev Java GUI now supports integration with Atlassian Crucible servers via a new AccuRev feature called Crucible Connection. This integration is designed to improve developer's productivity and alleviate the performance issues with creating and modifying code reviews using the Crucible web browser and accessing web application that is native to the Atlassian Crucible server. By using the REST API provided by Crucible application and the AccuRev Plug-In for Atlassian Crucible, the AccuRev Java GUI can now integrate with Atlassian Crucible by using HTTP and secure HTTPS connections (i.e. TLS v1.2).

Note: The AccuRev Plug-In for Atlassian Crucible must be installed as a managed add on for the Atlassian Crucible server for Crucible Connection to work properly, because the plugin is needed for Atlassian Crucible to interact with the AccuRev Server.

Back to top

How to enable Crucible Connection

The Crucible Connection feature can be enabled in the AccuRev Java GUI by accessing the AccuRev Preferences dialog box and entering Atlassian Crucible server and user information into the Code Review tab panel.

When the Enable code review integration check box is selected, users will see menu items that will enable them to send active file changes, transactions, and/or issues to New Reviews and Existing Reviews in relevant places throughout the AccuRev Java GUI.

Atlassian Crucible Project and Review information are retrieved from the Atlassian Crucible server and are filtered in the AccuRev Java GUI based on the AccuRev Depot being active for the various AccuRev views.

Back to top


For the AccuRev GUI, logger messages have been added. The possible logging levels are: Debug, Info, Error, Warn, and Fatal.

To enable this, users can change the log level in the log4j.xml file. The log4j.xml will be available in the location: \Atlassian\fecru-4.6.1.

Note: Logging cannot be enabled on Crucible versions before 4.1.2.


  1. Change INFO to DEBUG.

    <logger name="com.atlassian.crucible.plugins.scm">
       <level value="DEBUG"/>
  2. Restart Crucible.
  3. Logs will be available in the following path:


Back to top