FishEye 3.5 release notes

22 July 2014 

With great improvements in the user interface and new API calls for managing instances, we think this FishEye 3.5 release will delight both users and administrators.

If you are upgrading from an earlier version of FishEye, please read the FishEye upgrade guide and the End of Support Announcements for FishEye. The FishEye 3.5 changelog is at the bottom of this page.

 

More ADG goodness...

Browsing code is a core activity when you're using FishEye, so it's important for that experience to be as good as possible. For FishEye 3.5 we've applied the new Atlassian Design Guidelines to the file browser. Not only do you get a clearer overview of your files and directories, but the FishEye experience is now much more closely aligned with other Atlassian products, such as JIRA and Stash:

New REST APIs for automating administration

For FishEye 3.5, we've extended the FishEye REST APIs further with /projects and /permission-schemes/ endpoints.

Along with the /users//groups/ and  /repositories/ endpoints that were made available in the FishEye 3.3 and 3.4 releases, you can now manage the configuration of your FishEye instance automatically.

Note that the 'v1' REST API resources are deprecated and will be removed in a future release.

See the FishEye Crucible REST API.

 

Better integration with Atlassian Stash

In  FishEye 3.4 , we introduced a new integration with Stash that lets you index your Stash Git repositories in FishEye with just a single click.

Now, with FishEye 3.5, we're pushing the integration a step further by using Stash events to  trigger incremental indexing of your Git repositories in FishEye. When you add a Stash repository to FishEye, the configuration is optimized so that FishEye only requests new commits once Stash notifies that a push has occurred. You don't have to configure polling anymore, or set up FishEye web hooks in your Stash instance. You'll also get the best network performance straight off.

See Integrating FishEye with Bitbucket Server.

Optimized memory usage = Many more active repositories

We've added a new passivation mechanism that allows FishEye to take advantage of larger Java VM heaps. For large instances this provides a huge increase in the number of repositories that can be actively requesting data:


See How FishEye uses memory for details.

Small improvements

Platform upgrades

  • FishEye now supports Java 8. See Supported platforms.
  • FishEye no longer supports versions of JIRA earlier than JIRA 5.0.

Change log

This section will contain information about the FishEye 3.5 minor releases as they become available. These releases will be free to all customers with active FishEye software maintenance.

If you are upgrading from an earlier version of FishEye, please read the FishEye upgrade guide.

The issues listed below are just the highlights of all those that have been resolved for the FishEye 3.5.x releases.

21 January 2015 - FishEye 3.5.5

17 September 2014 - FishEye 3.5.4

27 August 2014 - FishEye 3.5.3

6 August 2014 - FishEye 3.5.2

23 July 2014 - FishEye 3.5.1

22 July 2014 - FishEye 3.5.0

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport