Meet FishEye and Crucible 3.0, a massive upgrade to our code search, visualization and review tools that will help development teams work faster, every day. This release provides developers with more powerful ways to track changes across all their code repositories, share knowledge, and accelerate collaboration cycles. Developers will find it easier to perform pre-commit reviews and benefit from huge indexing performance gains – especially for Subversion repositories. Come and meet the new FishEye and Crucible!
The FishEye and Crucible team have been laser-focused on improving dev speed for our users. Our aim is to optimize performance from the moment you start to index your repositories to when you close a code review. It’s important for us to continue to help you save valuable time in your development process.
In FishEye 2.8 we focused on improving load times on key pages like the activity streams and projects lists. Continuing our focus on performance in 2.9, we delivered improvements to shave off seconds for several common operations between JIRA, FishEye, and Crucible–specifically the source and review Tabs. Then in 2.10, we slashed server load and made every operation faster, especially for Enterprise teams: page loads, reviews and reports. We continue the performance theme in 3.0.
A newer, faster Subversion indexing engine
Take a deep breath Subversion users; you no longer have to wait for a full index of your Subversion repository in order to start using FishEye and Crucible. Our newest release uses intelligent indexing to make viewing your latest changesets and creating reviews available while the indexing is in still progress. Exhale!
Check out the difference from data tested on a load testing instance of FishEye and Crucible comparing index scanning times of 3.0 and 2.10.
The improvements bring these advantages to Subversion users:
- Get productive ASAP: Viewing recent changesets and creating reviews is 10 times faster.
- Understand progress: New progress screens give you a better understanding of how long it will take to index your repository.
- Faster JIRA integration: Information in your JIRA source and review tabs is available while indexing is being performed
Even more performance gains
We did not stop there. We want to make ensure FishEye and Crucible stay fast as you grow. A huge focus was put on improving concurrent performance. You will notice improvement across the common operations you use everyday like creating review and browsing commits.
- Faster source browsing: we upgraded our internal database (to InfinityDB-3), this means greater concurrent access speeds and a better browsing experience
- Quicker review creation: the techy details, we optimized some SQL statements when creating or modifying a review in Crucible. What it means to you, the time to create or modify a review is cut down to save you valuable time.
See some of the browsing improvements from a load testing server comparing FishEye and Crucible 3.0 to 2.10.
Streamlined pre-commit reviews
Simply put, a pre-commit (or patch) review means reviewing code changes before they are checked-in to a repository. Typically, teams adopt pre-commit reviews as part of their code review workflow for reasons such as:
- Catching defects early: Ensure other developers on your team will not get affected by defects or bugs that can be found during a review.
- Keeping code clean: Guarantee that all code that gets into the repository is of high quality.
- Enforcing process: Make sure that reviews are not indefinitely postponed, or pile up to the point of never getting done.
Command line interface (CLI) pre-commit reviews
Until today, Crucible has been handling pre-commit reviews by uploading patch files through the Crucible user interface. We wanted to streamline this process so developers can stay in the flow. Crucible 3.0 introduces the command line interface (CLI) tool which allows you to generate pre-commit reviews, or update existing ones from where you already are: the command line. No logging into Crucible, no context-switching. This shaves off valuable time from the review process, and keeps your coders coding.
The CLI pre-commit reviews works for all supported version control systems including Subversion, Perforce, CVS, Mercurial, and Git.
Iterative pre-commit reviews
Code reviews are naturally iterative, and pre-commit reviews are no different. Let’s face it: Almost all reviews find something that needs to be re-factored or reworked, and it’s not unusual for reviews to include several revisions. Crucible automatically tracks what you’ve reviewed at the file and revision level, as well as comments. This ensures that you’re presented with only the latest changes, and don’t have to wade through the rest. Crucible 3.0 makes it simple to manage reviews throughout the iterations:
- Outdated files: Know when a new revision is available and include it in the review with a single click.
- Tracking as you go: Crucible tracks which files and comments you’ve already covered, then resets them as new revisions or comments are added.
Iterative code review makes it simple for teams to collaborate around code changes in order to ensure the highest code quality.
A brand new experience
Following the lead of JIRA and Confluence, FishEye and Crucible 3.0 introduce a new user experience that follows the Atlassian Design Guidelines (ADG). The goal is simple: Put key elements front and center, so developers can stay in the flow and work faster. The improved design is just the beginning of making it easier to navigate FishEye and Crucible.
New global header
When logging into FishEye and Crucible, one of the first things you’ll notice is the new global header. Navigating FishEye and Crucible is simpler with quick access to recent repositories, projects, reviews, and people.
Many FishEye users connect to other Atlassian applications, like JIRA or Bamboo. Users can now easily switch between FishEye and JIRA–or any other Atlassian application–all from the FishEye and Crucible header. No more bookmarks in your browser; we do the job for you.
JIRA source and review tab redesign
The key ingredient to any source code manager is its relationship to issues. Many FishEye users link their source to JIRA, and close the loop between code changes and the tasks that prompted them. We wanted to simplify the experience but still give users the important information they need to make decisions around their issues.
Improve your dev speed with FishEye and Crucible 3.0
New to FishEye and Crucible? Start a free trial and get up and running in a matter of minutes.