TeamCity Digest #8

teamcity-digest

After some time, during which we released the anniversary TeamCity 10.0 (and then 10.0.1), we are resuming our TeamCity Digest series with the latest TeamCity-related blog posts and articles we’ve stumbled upon during the last couple of months.

Kevin Venter of Xero shares their team experience on running JMeter performance tests in TeamCity: Run JMeter performance tests on TeamCity.

Khalid Abuhakmeh, director of software development at RIMdev, has written a post describing how to run Gulp on a TeamCity build agent consistently every time, without installing it globally: Running Gulp On TeamCity.

Stéphane Erbrech has documented and shared his experience of using TeamCity official Docker images to run a TeamCity server and a Postgres database instance via Docker with data containers: Migrating TeamCity to docker with data containers.

On a similar note, @egregors shares Docker-compose configurations to set up a TeamCity server and minimal agent with PostgreSQL:

Jason St-Cyr of Sitecore recorded a quick screencast of using TeamCity shared resources feature:

A new TeamCity REST API client – FluentTC – has been developed and published by Boris Modylevsky: https://github.com/QualiSystems/FluentTc. Feel free to try it out and contribute.

Another interesting publication is a piece on integrating a UI testing solution Ranorex with TeamCity. The problem is that it requires access to an interactive desktop, which TeamCity, running under a Windows System account, doesn’t provide by default: Integrating Ranorex with TeamCity using PsExec.

A Salesforce engineer’s story on running automated regression tests on multiple TeamCity projects, each one pointing to a different environment using the environmental variables approach: How to handle Visual Studio configurations through TeamCity.

Howard van Rooijen of Endjin, our partner, provides a set of instructions on working with TeamCity backups: A Step by Step Guide to Automating TeamCity Backups.

And here is a script by Richie Lee that uses TeamCity and Octopus Deploy APIs to raise defects if a TeamCity build has failed: Using TeamCity To Raise Octopus Defects Updated.

See all TeamCity Digests.

This entry was posted in Blogroll, Digest. Bookmark the permalink.