This page lists the supported platforms for Crucible 4.5 and its minor releases.
Key: = Supported = Deprecated = Not Supported
Oracle JRE / JDK
Crucible requires the Java Runtime (JDK or JRE), version as noted. Pre-release/Early access versions of Java are not supported.
We highly recommend that you use the Oracle JVM (or OpenJDK for Linux only). Other Java implementations have not been tested.
You can download an Oracle Java Runtime.
For the OpenJDK, download and install instructions for Linux flavors are at http://openjdk.java.net/install/.
Support for Java 7 was removed in Crucible 3.9, as previously announced.
Java 9 is not supported yet, please track this feature request for updates.
1.8 (Linux only)
Although Crucible can be run in virtualized environments, Atlassian is not yet able to provide technical support for performance-related problems in a virtualized environment. If you do choose to run Crucible in a VM, please ensure that you choose a VM with good IO throughput.
Apple Mac OS X
Bundled; for evaluation use only
The Crucible built-in database, running HSQLDB, is somewhat susceptible to data loss during system crashes. We recommend that you do not use HSQLDB for production systems.
External databases are generally more resistant to data loss during a system crash and are more suited for production use.
See the Crucible Database documentation for further details.
MySQL Enterprise Server 5.5+
Support for PostgreSQL 8.3, 8.4, 9.0 and 9.1 was removed in Crucible 4.2. See End of Support Announcements for Crucible.
Support for SQL Server 2008, 2008 R2 was removed in Crucible 4.2. See End of Support Announcements for Crucible.
Microsoft Internet Explorer
Minimum screen resolution of 1024x768. Recommended screen resolution of 1280x768 or above.
Support for Internet Explorer 10 was removed in Crucible 4.3. See End of Support Announcements for Crucible.
Version Control Systems
Crucible 3.1, and later, do not support the native JavaHL 1.6 client.
See Native support for SVN for discussion.
Client version 2007.3 or later
188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
These are the versions of Git that we currently test Crucible against.
[Security vulnerability CVE-2014-9390] affects multiple Git versions. Crucible itself is not affected, however you should update your clients to a patched maintenance version: v188.8.131.52, v1.9.5, v2.0.5, v2.1.4and v2.2.1 or newer.
Git for Windows is the only supported distribution when running Crucible on Windows. Cygwin Git is not supported.
4.2 (since Fisheye 4.4.1), 4.2.3
3.0.2, 3.1.2, 3.2.4, 3.3.3, 3.4.2, 3.5.2, 3.6.3, 3.7.3, 3.8.4, 3.9.2
2.0.2, 2.1.2, 2.2.3, 2.3.2, 2.4, 2.5.2, 2.6.3, 2.7.2, 2.8.2, 2.9.1
These are the versions of Mercurial that we currently test Crucible against.
As of version 3.6.3, Crucible supports Mercurial 3.
Mercurial 2.1 has a bug that makes it incompatible with Crucible. Please use Mercurial 2.1.1 or later.
You should restart Crucible after upgrading Mercurial.
Crowd client library: 2.4.1
|From version 2.8.x, Fisheye bundles the Crowd 2.4.1 client library, and supports the Crowd 2.4.x server, and later versions.|
Jira Fisheye Plugin 6.1.0+
|The Jira Fisheye Plugin is bundled with Jira. If you are using earlier versions of Jira you can upgrade the plugin in Jira to get support for Crucible.|
Crucbile should ideally run on a dedicated server. The most important aspect for a large-repository deployment will be I/O speed. You definitely want a fast local HDD for Crucible's cache. Note that NFS and SAN are not supported.
1.8GHz or higher, a single core is sufficient. More cores or higher GHz will result in better load-handling ability.
1GB minimum, 2GB will provide performance "headroom". Your Java heap should be sized at 512MB.
Crucible's input/output is an important element of its overall performance. If Crucible accesses your repository remotely, make sure that the throughput is maximum and the latency minimum (ideally the servers are located in the same LAN, running at 100Mbps or faster).
|監視||Minimum screen resolution of 1024x768. Recommended screen resolution of 1280x768 or above.|
While some of our customers run Crucible on SPARC-based hardware, Atlassian only officially supports Crucible running on x86 hardware and 64-bit derivatives of x86 hardware.
Disk space requirement estimates
Disk space requirements for Crucible may vary due to a number of variables such as the repository implementation, file sizes, content types, the size of diffs and comments being stored. The following table contains some real-world examples of Crucible disk space consumption.
Codebase size (HEAD of trunk)
Fisheye index size
466 MB in 12151 files
115 MB in 11433 files
These disk space estimates are to be used as a guideline only. We recommend you monitor the disk space that your Crucible instance uses over time, as needs for your specific environment may vary. It may be necessary to allocate more space than indicated here.
Deployment Notes for Source Code Repositories
Crucible can also store uploaded files in its own database, removing the need for any kind of repository. A number of external databases are supported when Crucible is used with Fisheye. See the Fisheye Supported Platforms.
Fisheye/Crucible is a standalone Java program. It cannot be deployed to web application servers such as WebSphere, Weblogic or Tomcat.