![]() ![]() You definitely want a fast local HDD for Fisheye's cache. The most important aspect for a large-repository deployment will be I/O speed. Hardware requirementsįisheye should ideally run on a dedicated server. We do not provide support for Docker itself or problems with any Docker environment. We support the Atlassian Docker templates and can help with FishEye related problems. You can use official images to deploy FishEye in a Docker container, or customize a Docker deployment on your own. ![]() If you are using a version of Jira earlier than Jira 6.4 you can upgrade the plugin in Jira to get support for Fisheye. Note that the Jira Fisheye Plugin is bundled with Jira. Communication the other way, from Jira to Fisheye, depends on the Jira Fisheye Plugin. Read more about it in:įisheye to Jira communication requires Jira 6.4.x or later. Mercurial on Windows does not provide support for non-ASCII characters in file names and paths. SQL Server 2019 is supported since Fisheye 4.8.5. Oracle 19c is supported since Fisheye 4.8.5. PostgreSQL 13&14 are supported since Fisheye 4.8.9. PostgreSQL 12 is supported since Fisheye 4.8.5. See the Fisheye Database documentation for further details. We recommend that you do not use HSQLDB for production systems.Įxternal databases (such as MySQL) are generally more resistant to data loss during a system crash. The Fisheye built-in database, running HSQLDB, is somewhat susceptible to data loss during system crashes. If you do choose to run Fisheye in a VM, please ensure that you choose a VM with good IO throughput. Although Fisheye can be run in virtualized environments, Atlassian is not yet able to provide technical support for performance-related problems in a virtualized environment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |