git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Code review tool recommendations - replacement for crucible?

From
Andreas Krey <a.krey@gmx.de>
Date
Jun 16, 2016, 09:41 UTC
Message-ID
<20160616094108.GA14661@inner.h.apk.li>
Hi all,

I'm looking for pointers to review tools that work with git (obviously), and can deal sensibly with bigger reviews. Things we need:

- Ability to split (set of) commits into multiple reviews,
  so parts of changes can be reviewed by the respective owners
  (or assign different reviewers to different files/subtrees
  in a review).
- Tracking of files (or changes) already reviewed (due to the large numbers),
  and of the handling of issues found so far.
- Support incremental reviews, not just e.g. over the content of a
  pull request (bitbucket) When review comments are processed people
  want to be able to only review that change, and not to be forced
  to find that change in the entire previous changeset without
  the tool's support.

We were mostly content with atlassian crucible so far, but it simply fails to index[1] our large product repo (5+ Gb) so we switched to just give it diffs to review, and it fails to properly display renames, and fails in a few minor but annoying ways in dealing with these big reviews.

Any pointers?
- Andreas
[1] Crucible seems to be svn-centric, and the mapping
    from git to svn changesets they use internally
    apparently is O(n^{too much}) - just indexing
    a new branch identical to an existing one takes
    hours here.
-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
Next: Richard Ipsum
Message 1 of 3 in “Code review tool recommendations - replacement for crucible?”
  1. Andreas KreyJun 16, 2016
  2. Richard IpsumJun 16, 2016
  3. Andreas KreyJun 16, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.