4

In our office we use a custom Geckoboard to display information about our current build status from our TeamCity 8 build server.

We display recent check-ins/changes, using the following REST query: http://teamcity.internal.com:8080/httpAuth/app/rest/changes?project:ProjectName&locator=count:10

We also calculate the last time the build was broken with this REST query: http://teamcity.internal.com:8080/httpAuth/app/rest/builds?locator=project:ProjectName

However what we've not just been able to do is link the two.

In other words:

  • For recent changes to determine if the checkin lead to a broken build
  • For the last time the build was broken determine who made that checkin
Peter Bridger
  • 9,123
  • 14
  • 57
  • 89
  • I'm not sure that this is even possible. Depending on your build process and team size, there could have been dozens of commits between builds, and any one of them could have broken the build. Team city's web interface offers a list of candidates for build-breakers. – Software Engineer Mar 20 '14 at 15:33
  • Each commit will trigger a build - so can't a broken build be traced back to the commit? – Peter Bridger Mar 20 '14 at 16:47

1 Answers1

0

Based on the source code here and documentation here

I believe you want something like the following

http://teamcity.internal.com:8080/httpAuth/app/rest/changes?locator=build:(status:FAILED,project:ProjectName,lookupLimit:1)

This should return the changes associated with the last FAILED build, I haven't tested because I don't use TeamCity.

Also see the following StackOverflow question in order to get changes for a specific build.

Community
  • 1
  • 1
Appleman1234
  • 15,946
  • 45
  • 67