The fact that you’re reading this is highly suspicious. Wouldn’t you rather be coding right now? Are you really a developer, or are you some alien life form in an over-worn “There’s no place like 127.0.0.1″ t-shirt masquerading as a coder?

See, we’ve been made to understand that, more than anything, devs just want to get back to coding. We also understand how hard it can be to keep a growing dev team flowing smoothly as new members join and new features are coded. Teams need a common interface for browsing repositories, tracking changes and reviewing each other’s code. And that, my new alien overlord, is why we built FishEye & Crucible 2.10.

Take a Load Off

FeCru2.10-REST-trigger-repository-indexing-1In the 2.8 and 2.9 releases, we removed architectural bottlenecks so FishEye and Crucible can keep up with the growing size of our customers’ repositories. Not only did we continue core performance improvements in 2.10, we added a new REST endpoint that gives your hard-working servers a little relief.

Instead of polling repositories once a minute, you can now trigger re-indexing only when something in your repo has actually changed. We even added support for triggering indexes from cloud-dwelling repositories on Bitbucket and Github. Optimizing FishEye and Crucible with post-commit hooks for indexing slashes server load and makes every operation faster, especially for Enterprise teams: page loads, reviews, reports, teleports… wait, strike that last one.

FeCru2.10-bitbucket-integration-fisheye

In the same spirit, we added a limit on the number of files that can be included in a Crucible review. But don’t worry: 800 files is far more than you’d want to review anyway (unless you are a Cylon…). By disallowing reviews against whole-repository commits like initial imports, branch creation or merges, your instance – and your productivity – is further protected against slowdowns.

Ludicrous Speed

But our quest for ultimate dev-speed doesn’t stop there. Developers all over the universe use of FishEye’s smart commits to create, update, and resolve issues and reviews programmatically. Now the same applies to review objectives Crucible. Use the smart commit syntax to add objectives to reviews as you’re creating them, or to existing reviews – without having to switch over to Crucible.

FeCru2.10-inline-issue-creation-crucibleAnd speaking of context switches, we threw another one out the airlock: now you can create JIRA issues right from the Crucible review you’re working on. Eminently logical.

All Your Code Are Belong to JIRA

Like 20,000 other teams across the galaxy, we use JIRA every day. So we know how important it is for FishEye and Crucible to integrate with JIRA as much as possible. With 2.10, associating all your instances and projects is easier than ever.

Connect them using Application Links, and that’s it. No need to meticulously map individual projects. Or install plugins. Or subscribe to gadgets. (Save those braincells for coding – the mothership needs your synapses to be well-rested.) With just the application link, you’ll see commit and review info inside issues, jump from issue to commit to review with a single click, and enjoy all the other benefits of integrated development tools.

Thanks For All the Fish(Eye)

That’s a lot to grok, but we’re sure your enlarged alien brain can handle it. We hope you enjoy using FishEye and Crucible 2.10 as much as we’ve enjoyed building them! Upgrade today – you’ll be kicking out fixes and features faster than you can make the Kessel run.

FeCru2.10CTA

Already using FishEye or Crucible? Check out our full FishEye and Crucible release notes to get started.