Crucible 4.2 release notes

28 September 2016

With Crucible 4.2 your reviews will be faster and more effective! Comments can be marked as Unresolved, so no review-related task will ever be forgotten anymore. To make repository management even easier, Crucible now allows repositories to be renamed. We improved Bitbucket Server integration, fixed a number of bugs and made other improvements.

If you are updating an earlier version of Crucible, please refer to the Crucible upgrade guide and the End of Support Announcements for Crucible. The Crucible 4.2 changelog is below.

Track work still to be done

The code review process in Crucible very often requires some additional actions (e.g. corrections, tests, updates) to be performed before a review can be completed. To make tracking of these actions more efficient with Crucible 4.2, both the author and the reviewers can mark comments that need resolution.

Once the requested action has been addressed, it can be easily indicated to all review participants by marking the comment as "Resolved".

Use the improved review Activity with "Unresolved" and "Resolved" filters to see outstanding and already resolved items in one place.

Read more about resolving comments.

Repository renaming

Over time projects and libraries tend to be split, merged or simply moved or renamed because their purpose changes. The same happens to repositories - it's natural that some may get renamed over time. In Crucible it is now possible to rename a repository, so that it can reflect its current name in the remote SCM. The rename operation is instantaneous and doesn't require any further actions (such as reindexing).

Review workflow conditions API

Crucible 4.2 gives you a much more powerful way of managing your review workflows. It introduces a new plugin module, which allows developers to easily hook into the review transition process and prevent transitions from happening under certain, programmable conditions. Learn how to write new workflow condition plugins with the Workflow Conditions Tutorial.

Improved Bitbucket Server integrations

Since Flexible Repository Management was introduced in Crucible 4.1, we wanted to unlock full administration opportunities for repository-level administrators. With Crucible 4.2, the Bitbucket Server repositories tab in the administration settings is now available to repository-level administrators, so they can easily add Bitbucket Server repositories to Crucible with just a few clicks.

For every Bitbucket Server repository added to Crucible, the Bitbucket Server repositories tab shows all the corresponding Crucible repositories that the user has admin permission to view.

Small improvements

Searching for text via the browser

Search for text using the browser (cmd + f / ctrl + f dialogs) has been significantly improved for Crucible pages. 

Change log

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

If you are upgrading from an earlier version of Crucible, please read the Crucible upgrade guide and the End of Support Announcements for Crucible.

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

31 August 2018 - Crucible 4.2.3

T Key Summary

21 March 2018 - Crucible 4.2.2

T Key Summary

9 November 2016 - Crucible 4.2.1

This release contains bug fixes shared between FishEye and Crucible. See FishEye 4.2.1 release notes for details.

28 September 2016 - Crucible 4.2.0

T Key Summary

Last modified on Aug 31, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.