TeamCity Digest #8
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.
Subscribe to Blog updates
Test Automation with TeamCity
TeamCity offers a number of ways to help you work with tests. First of all, it presents the test results for each build execution so it’s easy to analyze what happened and why something has failed. Besides that, TeamCity includes advanced features like code coverage, flaky test detection, metadata i…
Getting Started with TeamCity TestDrive
⚠️ Update from October 12, 2020: TeamCity TestDrive has been deprecated. If you are looking for a simple way to try TeamCity without downloading and installing it on a server, please consider giving a try to TeamCity Cloud. TeamCity Cloud is a fully-managed CI/CD solution that automati…
Building Go programs in TeamCity
TeamCity provides support for multiple technologies and programming languages. In TeamCity 2019.1, support for Go has been included in the distribution. In this blog post, we will explain how to configure TeamCity to work with Go programs.…
Building GitHub pull requests with TeamCity
The support for pull requests in TeamCity was first implemented for GitHub as an external plugin. Starting with TeamCity version 2018.2 the plugin is bundled in the distribution package with no need to install the external plugin. The functionality has since been extended in version 2019.1 to suppor…