This page lists the supported platforms for Crucible 4.8 and its minor releases. We cannot ensure the stability of Crucible used with a platform or a versions that is not mentioned in this page.
Key: = Supported = Deprecated = Not Supported
Crucible requires the Java Runtime (JDK or JRE), version as noted. Pre-release/early access versions of Java are not supported. We recommend that you use the Oracle JDK or Adopt OpenJDK as these are implementations we test Crucible against.
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 chose 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.
5.6, 5.7 Enterprise Server
5.6, 5.7 Community Server
12c R1, R2
SQL Server 2016 and 2017 are supported since Crucible 4.7.1.
Version Control Systems
Native JavaHL 1.8, 1.9, 1.10
Native JavaHL 1.7
2007.3 〜 2017.2
The Server must support the ztag tagged protocol.
Perforce Streams are not supported (FE-3886).
1.9.5, 2.0.5, 2.1.4, 2.2.3, 2.3.10, 2.4.12, 2.5.6
Git for Windows is the only supported distribution when running Crucible on Windows. Cygwin Git is not supported.
3.7.3, 3.8.4, 3.9.2
2.8.2, 2.9.1, 3.0.2, 3.1.2, 3.2.4, 3.3.3, 3.4.2, 3.5.2, 3.6.3
These are the versions of Mercurial that we currently test Crucible against.
You should restart Crucible after upgrading Mercurial.
Crowd client library: 2.4.1
Jira Fisheye Plugin 6.1.0+
Jira 6.4 以降
|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.|
Crucible 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.