Adventures of a wannabe geek!

Ranting within

TeamCitySharp v0.2

Hot on the heels of the first release of TeamCitySharp, a new update has been released for the project to nuget. There were 2 major additions to the project both contributed via pull requests on Github.

Introduction of Build Locator

This makes the protocol for obtaining build information easier as we use the locator in the url rather than trying to build a query string manually. Previously we built a query string as follows:

http://myserver.com/httpAuth/app/rest/buildTypes/id:bt437/builds?status=SUCCESS

This would get the successful builds for build config id 437. This has now been replaced by the following query string:

http://myserver.com/httpAuth/app/rest/builds?locator=buildType:id:bt437,status:SUCCESS

Thanks must go to Simon Bartlett for this addition to the codebase. The existing methods will work in this way as the code behind the public methods has been changed to us the build locator pattern. Therefore you can still call the method:

Behind the scenes TeamCitySharp does the following call:

 

New Sample Build Monitor

There is now a new project included in the source code. This project is a sample implementation of a build monitor using TeamCitySharp based on MVC3 and Knockout.js. Thanks to Barry Mooring for contributing this sample to the project.

In order to use the build monitor you just need to go to the settings file and add the TeamCity url, username and password.

This gives a look and feel as follows:

image

 

You can download the source from Github or via nuget (install-package TeamCitySharp). Please feel free to leave feedback about what you feel it is lacking or what you don’t like about the project. This library will only be able to get better through help from users.