Getting text changeset list from a build

Hi There,

Our validation folks have asked me for a text list change set of a given build, or in some cases a range of builds, to include the repository commit comments and associated files and possibly file CI comments. We are using SVN however we do have a TFS repository as well, but not for this task.. This data is accessable via the UI, but not in a useable form.

I have considered just putting in a build step to capture this, but nothing is in concrete. Wide open on ideas.

I have searched this site with every keyword I can think of to find examples or ideas on how to do this. I have also, and this is all new to me, looked at some of the APIs. No luck.

Can someone please point me in the right direction for doing this?

Much appreciated,

Len

5 comments
Comment actions Permalink

Hi Len

Have made a similar request myself
See  http://youtrack.jetbrains.com/issue/TW-23865

If you create a build step that includes all the VCS    of the builds that make up your project to can see a list of all the changes in the change log  tab ( nice detail graphical list)

Like you just wish there was an easy way to export this list.

Stewart

0
Comment actions Permalink

Hi

As said in the issue comments, TeamCity allows to obrain this data via REST API.

0
Comment actions Permalink

Thanks for the replies!

I have looked at the REST API and found everything in the world - except what I need!

Can you point me precisely to what I am missing? As I said, this REST API stuff is all new to me!

Thanks,

Len

0
Comment actions Permalink

> Can you point me precisely to what I am missing? As I said, this REST API stuff is all new to me!

 

I too need this information. Has this ever been addressed?

0
Comment actions Permalink

The changeset can be pulled via the /app/rest/changes?locator=build:(id:<buildId>) endpoint, as detailed here: https://www.jetbrains.com/help/teamcity/rest-api.html#RESTAPI-Changes

 

The "build" locator doesn't just accept the ID, but accepts the usual build locator options, so you can pass something like "affectedProject:<id>" or anything that will match the set of builds you would like to get. Remember that you can expand the items received (if they have subchildren) by adding the "fields" parameter and specifying the names that you would like to expand.

0

Please sign in to leave a comment.