Question

Kiln 2.9 is almost out, and it's bringing some major changes to how code reviews work in Kiln. What does this mean for the API?

Answer 1

In the 1.0 API, I could find the set of reviews associated with a particular changeset by looking at the ixReviews property in the changeset record.

Will this continue to work for the new Reviews? (Ie, will I see sReviews in a changeset record's ixReviews array?)

Answer 2

I do not like the fact that we will no longer get our review notification through fogbugz. I do not want two task lists to keep my eye on. Personally I think it sucks...

Answer 3

In Kiln 2.9, we've made a major change to how code reviews work: when you create a code review, it's no longer backed by a FogBugz case. Code Reviews are now completely separated from cases. You'll manage your code reviews entirely through Kiln, with a new and improved interface.

This change necessitated a backwards-incompatible change to Kiln's Reviews API. You can find the new API documentation in the Kiln Developers Wiki. Here are the highlights:

• The old API has been removed in Kiln 2.9. Any call to Api/1.0/Review/... will return a VersionTooLow error.
• The new API exists requires an API version of 2.0 or higher (i.e. Api/2.0/Review/...).
• Creating a new review no longer opens a case in FogBugz.
• Reviews are uniquely identified by sReview, a string in one of the following two formats:
  1. a string containing a positive integer (e.g. "2" or "500"), corresponding to the FogBugz case number of this review. This format will only be used to reviews that were created in older versions of Kiln.
  2. "K" followed by a positive integer (e.g. "K2" or "K500"), identifying a review that does not have a FogBugz case. All reviews created with the Reviews API 2.0 will use this format.
• Other parts of the API are not affected by this change (such as repository and project management), and continue to be a 1.0-version API.

While we strive for backwards compatibility wherever possible, this major upgrade made that impossible. We understand that this breaking change may cause you some inconvenience. If you need assistance in upgrading scripts or tools to the new API, please contact Fog Creek Support and we'll be happy to help.