nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

View review status for all ancestors in Crucible with Mercurial

John Slade

We are using Crucible with Mercurial and I'd like to see the status (i.e. reviewed or not) of all changesets that are ancestors of a given point. This is so before doing a merge into our mainline I can see that all the changes about to be merged have been succesfully reviewed.

I can partially do this in the commit graph but you cannot combine the "lineage" and the "reviewed changeset" views.

Essentially I'd like to do hg log --rev "ancestors(<rev>)" and get the review status of every commit returned. Is this part of the front end or do I need to write a script to use the API?

Accepted answers

All comments

Alexander Taler

I had the same requirement (with Subversion) and ended up writing a plugin which generates reports by branch, because it wasn't that easy to solve. You can find it on the Marketplace here:

https://marketplace.atlassian.com/plugins/biz.deref.flyover.flyoverForCrucible

I've tested and used it with Subversion and Git, but not extensively with Mercurial, so let me know if you encounter any issues due to peculiarities in Mercurial.

If you've got Fisheye as well I believe the reporting functionality there may help you but I'm not familiar with the details.

John Slade

Great plugin - currently evaluating the trial version and we'll probably end up buying a license as it already looks very useful.

However, it doesn't fulfil the exact thing I was looking for (unless I am missing something in the report creation). I'm interested in the review history of changesets that were merged into a branch (the changeset being made another named branch originally). The changeset data can be extracted from the DVCS tool directly (although I don't see it in Cruicble or Fisheye) - "hg log --rev ancestors()" in Mercurial or "git log --ancestry-path" in Git.

Alexander Taler

Yes you're correct, the plugin won't follow ancestry across branches. It's not a straightforward test in Crucible, but it should be possible, and I can see how it would be useful.

I should run some tests to see exactly what Crucible/Fisheye consider as being on a branch since the concept is very different between Subversion and the DVCSes.