Supported platforms

Still need help?

The Atlassian Community is here for you.

Ask the community

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(tick) = Supported  (warning) = Deprecated   (error) = Not Supported

Java



Oracle Java

(tick) 1.8

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.

Please note:

  • Ensure that you've set your max heap size (--Xmx) to a reasonable value, considering the memory requirements of your system.
  • You'll need the JDK for the Crucible JSP source download.
  • For OpenJDK, you'll need the DejaVu font package installed. Installation instructions can be found here: http://dejavu-fonts.org/wiki/Download.

OpenJDK

(tick) 1.8

Operating Systems



Microsoft Windows

(tick)

  • Crucible is a pure Java application and should run on any platform provided the requirements for the JRE or JDK are satisfied.

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.

Linux

(tick)

Apple Mac OS X

(tick)

Databases



HSQLDB

(tick) 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

(tick) 5.6, 5.7 Enterprise Server

(tick) 5.6, 5.7 Community Server

(error) Maria, Percona


PostgreSQL

(tick) 11

(tick) 10, 10.5

(tick) 9.6

(warning) 9.4, 9.5


Oracle

(tick) 12c R1, R2


SQL Server

(tick) 2017

(tick) 2016

(warning) 2012, 2014

SQL Server 2016 and 2017 are supported since Crucible 4.7.1.

Web browsers



Internet Explorer

(warning) 11.0


Microsoft Edge(tick) Latest stable version supported

Mozilla Firefox

(tick) Latest stable version supported


Safari

(tick) Latest stable version supported


Chrome

(tick) Latest stable version supported


Version Control Systems



Subversion (SVN)

Server:
(tick) 1.8, 1.9, 1.10

(warning) 1.7

Client:
(tick) SVNKit (bundled & the default)

(tick) Native JavaHL 1.8, 1.9, 1.10

(warning) Native JavaHL 1.7


CVS
(and CVSNT)

(tick) All versions


Perforce

(tick) 2018.x, 2019.x

(warning) 2007.3 - 2017.2

The Server must support the ztag tagged protocol.

(error) Perforce Streams are not supported (FE-3886).

Git

(tick) 2.23.0

(tick) 2.22.1

(tick) 2.21.0

(tick) 2.20.1

(tick) 2.19.1

(tick) 2.18.1

(tick) 2.17.2

(tick) 2.16.5

(tick) 2.15.3

(tick) 2.14.5

(tick) 2.13.7

(tick) 2.12.5

(tick) 2.11.4

(tick) 2.10.5

(tick) 2.9.5

(tick) 2.8.6

(tick) 2.7.6

(tick) 2.6.7

(warning) 1.9.5, 2.0.5, 2.1.4, 2.2.3, 2.3.10, 2.4.12, 2.5.6

[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: v1.8.5.6, 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.




Mercurial

(tick) 4.5.3

(tick) 4.4.2

(tick) 4.3.3

(tick) 4.2.3

(tick) 4.1.3

(tick) 4.0.2

(tick) 3.7.3, 3.8.4, 3.9.2

(warning) 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.

Atlassian applications

Crowd

(tick) Crowd 2.4.x+

(tick) Crowd client library: 2.4.1


Jira

(tick) Jira Fisheye Plugin 6.1.0+

(tick) 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.

Hardware requirements

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.

Component

Specifications

CPU

1.8GHz or higher, a single core is sufficient. More cores or higher GHz will result in better load-handling ability.

RAM

1GB minimum, 2GB will provide performance "headroom". Your Java heap should be sized at 512MB.

I/O

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).

MonitorMinimum 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.

Repository technology

Commits

Codebase size (HEAD of trunk)

Fisheye index size

Subversion

14386

466 MB in 12151 files

647 MB

CVS

8210

115 MB in 11433 files

220 MB

(warning) 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.

WAR deployment

Fisheye/Crucible is a standalone Java program. It cannot be deployed to web application servers such as WebSphere, Weblogic or Tomcat.

Single sign on with Atlassian Crowd

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.
Last modified on Dec 5, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.