This documentation relates to an earlier version of Crucible.
View

Unknown macro: {spacejump}

or visit the current documentation home.

This page describes the initial configuration of Crucible, including the steps contained in the Crucible setup wizard.

Running Crucible

This document assumes you have extracted your Crucible zip file into a directory called /FISHEYE_HOME/.

To run Crucible for the first time:

  • Windows の場合
    C:\> cd FISHEYE_HOME\bin
    C:\FISHEYE_HOME\bin> run.bat
    
  • On UNIX-based systems:
    $ cd /FISHEYE_HOME/bin
    $ ./run.sh
    

Once started, Crucible will run its own HTTP web server on port 8060. You can access Crucible immediately by going to http://HOSTNAME:8060/ in a browser.

By default, Crucible will listen on port 8060 for HTTP requests. It also listens on 127.0.0.1:8059 as a control port. You can configure both of these in the Administration screens, or by editing /FISHEYE_HOME/config.xml and restarting Crucible.

On this page:

Supplying Administration Password and License Key

The first time you access the Crucible web server (http://HOSTNAME:8060/) you will see a screen like this and you will be asked for two things:

  • An administrator password. This password controls access to the administration screens.
  • A license key. Please note your server ID, shown on the screen above. You can then get a Crucible evaluation license key from the Atlassian website.

Integrating Crucible with JIRA

アプリケーションを JIRA に接続し、JIRA で情報を共有しながらユーザーの管理もできます。JIRA がインストールされている場合は、アプリケーションのインストール時、設定ウィザードに JIRA との連携設定ボタンが自動的に表示されます。これは、ほとんどのオプションを標準条件とした状態で JIRA との連携を設定するためのものです。

また、JIRA への接続設定はアプリケーションの管理画面からでも行えます。その場合、接続は個々に設定する必要があります。連携プロセスは 2 箇所で行います。

  • JIRA - アプリケーション間のP2P リンク:情報共有と連携機能を円滑にします。このリンクはアプリケーションリンクから設定します。
  • アプリケーション - JIRA 間のクライアントサーバーリンク:ユーザーとグループの管理を JIRA サーバーに割り当てます。

要件: JIRA 4.3 以降が必要です。

For detailed instructions and troubleshooting, see Configuring JIRA Integration in the Setup Wizard.

Accessing the Administration Pages

Once you have set up an administrator password, you can access the administration screens at http://HOSTNAME:8060/admin/.

One of your first steps will be to set up access to a source-control repository, or an alternative form of code storage such as the local file system or Atlassian Confluence.

The instructions for configuring your repositories are different, depending on your Crucible setup:

The following topics describe how to configure repositories that are not managed by FishEye. These instructions apply to all three setups described above:

Setting Up Users

On initial setup of Crucible, you can choose to integrate your user base with JIRA, as described above. If you do that, the setup process will copy across your JIRA users into Crucible.

If you do not integrate with JIRA in the setup process, Crucible will not have any users defined after setup.

Adding user accounts is done via the administration screens or by configuring Crucible/FishEye to use external authentication.

To add users:

  1. Open the Crucible administration screen at http://HOSTNAME:8060/admin/.
  2. Click 'Users/Security' under 'Global Settings' in the 'Admin Menu'.

Read more details about the different ways of creating users in the FishEye documentation.

Understanding Notifications and Setting Up Your Mail Server

Crucible can email each review participant on a range of changes. Each user can then set up their own preferences. This is described in the guide to the user profile guide.

First, you must set up the SMTP Server.

Crucible を利用する

You can access Crucible immediately by going to http://HOSTNAME:8060/ in a browser.

Or you can go directly into the Crucible homepage at http://HOSTNAME:8060/cru.

Stopping Crucible

To stop the Crucible server:

  • Windows の場合
    C:\> cd FISHEYE_HOME\bin
    C:\FISHEYE_HOME\bin> stop.bat
    
  • On UNIX-based systems:
    $ cd /FISHEYE_HOME/bin
    $ ./stop.sh
    

Information about FishEye Integration with Crucible

If you want to know more about how Crucible and FishEye interact, refer to our explanation of how Crucible works with FishEye.

3 Comments

  1. Kevin Behrens

    Is it Atlassian's recommendation to use an external db?

    1. Erik van Zijst

      We use PostgreSQL on our own Crucible instances, but don't officially endorse one database over another at the moment.

      When choosing a database, you should consider that the default, built-in HSQLDB is not concurrent (it processes queries one at a time), making it less scalable than an external database. Also, HSQLDB may be more susceptible to file system corruption when Crucible is killed by force (kill -9).

      cheers,
      Erik

  2. Kevin P. Fleming

    Is there going to be a Confluence SCM plugin for Confluence 3.x? We'd really like to be able to use Crucible for wiki page reviews.