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; } } }

Crucible - get list of changesets / revisions in a review

Richard Bradley

How can I get an accurate and exhaustive list of all changesets / revisions which have been added to a review?

I can browse all the files in the review, and note the commit hashes (with git) at the top of each page, but I'd like to be able to see this more easily.

Is there anywhere that this is listed? An API call would be acceptible.

I am using "Atlassian FishEye analysis with Crucible code review. (Version:3.1.4 Build:20131008122028 2013-10-08)"

Accepted answers

All comments

Felipe Kraemer

Hi Richard,

You can use this REST API call. This will return, among other things, a list of files and their changesets.

I hope this helps!

Richard Bradley

Thanks, that looks promising, but I need a bit more help getting to the REST API. I have a review at https://jira.mycompany.com/fisheye/cru/ABC-123 -- so where would the REST API live? I have tried https://jira.mycompany.com/fisheye/cru/rest-service/reviews-v1/ABC-123 and quite a few similar URLs (including https://jira.mycompany.com/fisheye/cru/rest-service/ ), but they all give me "There is no Action mapped for namespace /cru and action name rest-service.". How can I make this work?

Felipe Kraemer

Hi Richard,

Looks like you have a fisheye context in your URL, so the complete URL should be like this:

https://jira.mycompany.com/fisheye/rest-service/reviews-v1/ABC-123/details

Basically, the REST API /rest-service/reviews-v1/ABC-123/details should be added right after your FishEye site URL, which is https://jira.mycompany.com/fisheye.

Please make sure to log into your instance at https://jira.mycompany.com/fisheye/login before running the REST API command above.

I hope this helps!

Richard Bradley

Thanks very much, that does return all commit hashes in the review (grouped by filename, so I'll have to do a bit of processing to get a distinct list of all commits that have been added to the review, but the data is in there).

Alexander Taler

Be aware that the listed revisions are not exactly those that have been added to the review. For example, if you're using Subversion and add revision 2507 of a single file to the review, the REST API will also return the previous revision of that file, e.g. 2290 might be included also.

Basically, revisions are grouped, and the first revision of each group is the context for the following ones, so play around with the output until you understand it.

Also, I have raised a bug about this behaviour, which you might want to be aware of:

https://jira.atlassian.com/browse/CRUC-6363

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

fisheye-crucible