Today we are pleased to announce the latest release of FishEye and Crucible. FishEye and Crucible give agile teams a powerful way to browse, search, share and review source code. Tight integration with the JIRA issue tracker gives teams traceability between issues, stories and source, regardless of your source code management system(s) – Git, Subversion, CVS, Mercurial or Perforce. FishEye 2.9 and Crucible 2.9 have improved integration with JIRA, enabling development teams to move faster and be more productive.
There are loads of things that can get in the way of your team’s productivity – but configuring your development tools shouldn’t be one of them. Administrators are routinely looking for ways to save time, cut down on common requests and get their development teams up and running quickly. The FishEye and Crucible team has delivered a set of new features to make system administrators’ lives a whole lot easier by simplifying the integration between FishEye, Crucible and JIRA.
- Save time: teams with large repositories and projects no longer need to create and maintain multiple links between projects in JIRA and repositories in FishEye, this is now done automatically.
- Cut down on common requests: never get another request to connect a FishEye or Crucible project to a JIRA project. Your JIRA instance now gets data from all projects existing on your FishEye and Crucible server automatically – no mapping required.
Seamless integration with JIRA unites developers and non-technical project team members around the code and the activity they track together as a team. Simply linking your JIRA instance to FishEye and Crucible gets you code, review and issue traceability.
- Full development traceability: code, peer reviews and JIRA issues come together to provide a 360-degree view of your team’s work.
- Cross linking between JIRA, FishEye and Crucible: we put the information you need where you’re already working. While working in JIRA, one click on the Source Tab takes you directly into any changeset, diff, or review in FishEye and Crucible where you can also see detailed information on issues.
Continuing our focus on performance, this release delivers improvements to strip off seconds for several common operations between JIRA, FishEye and Crucible – specifically the Source and Review Tabs. Large instances with multiple repositories, each with many changesets will get relevant information up to 10x faster when viewing the Source and Review tabs in JIRA. Check out the difference from data tested on a load testing instance of FishEye and Crucible with multiple repositories and changesets.
Faster Review Creation for Larger Teams
Building time for peer code reviews into a project schedule is hard enough, so the process has to be simple and easy. Our developers want efficient code reviews so they can get back to coding – we reckon yours do too. So we asked ourselves: How can we save developers time when creating reviews?
We realized that developers know instinctively what needs to be reviewed and what doesn’t. So we axed the “Suggested Reviews” step when creating reviews – a step that was taxing both for the review creator and the Crucible instance itself, especially for larger instances. By removing it, we streamlined performance for both human and machine.
Try FishEye and Crucible 2.9
New to FishEye or Crucible? Start a free trial today and get up and running in minutes.