Crucible 2.7 : Crucible 2.0 Beta Reviewer's Guide

Crucible 2.0 Beta is a public development release leading up to Crucible 2.0. For all production use and testing of Crucible, please use the latest official release.

Do not use in production.
Beta releases should not be used in production environments.

Please also take note of the following information:

  • Beta releases are not safe — Beta releases are snapshots of the ongoing Crucible development process. As such:
    • While we try to keep these releases stable, they have not undergone the same degree of testing as a full release.
    • Features in development releases may be incomplete, or may change or be removed before the next full release.
    • FireFox 3 and Safari are the only browsers supported.

Thank you for your interest in the Crucible 2.0 Beta. This page contains some direction on what is ready for testing, what the known issues are and how you can submit feedback.

Known Issues

This is a list of known issues with the Crucible 2.0 Beta; please do not raise requests related to these as solutions for them are already under way.

  • REST API updates are not fully functional; you can't access various features from the IDE Connectors or other technology that depends on REST. The features affected include marking comments as read, Iterative Reviews and Activity Streams. Also, JSON support is alpha at this stage.
  • JIRA sub-tasks integration will not work on JIRA instances where the JIRA General Setting "allow unassigned issues" is set to 'OFF'.
  • Sorting functionality is only partially functional; when you are trying to sort content — such as review lists on the reviews page, content on the dashboard and project dashboard — the sorting of content by name, date and so on only applies to the current page of results. To mitigate this, narrow down your searches so that you only have one page of results. This will be revised to have server-side sorting.
  • You can't create reviews with files or changesets from multiple repositories.

Features Ready For Testing

The following features in the Crucible 2.0 Beta are relatively hardened and using these thoroughly will help contribute to the final product.

  • Iterative Reviews; create a review on multiple revisions of a changeset, to see the history and evolution of the code in-line.
  • Activity Streams; see review activity, code commits and JIRA activity (when properly configured) on the Dashboard.
  • External Database Support; You can now store Crucible's internal data in a MySQL or PostgreSQL database, as an alternative to the built-in HSQLDB.
  • Crucible can assist you in updating reviews by suggesting changesets that are likely related to your reviews.
  • Reviews can now have a Due Date. Reviews that are overdue will show up in red on the reviewer's dashboards to minimise the chance of reviews getting stale.
  • Stars; add colleagues, reviews and files to your favourites list, then view updates related to them as a feed.
  • Charlietars; the automatically generated Crucible avatars should work smoothly. Also, you can sign up to Globally Recognised Avatars (http://www.gravatar.com) to upload a profile image and use that instead of the Charlie image.
  • Scheduled Backups; you can now easily set Crucible to backup data periodically using a simple calendar function in the user interface.

Submitting feedback

To submit feedback on the Crucible 2.0 Beta, please use the Crucible Forums.