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: 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.

Posted in Blogroll, Digest | Comments Off on TeamCity Digest #8

TeamCity 10.0.1 Update

We have prepared a 10.0.1 bugfix update based on the feedback we received from those who upgraded. The most critical issues found in 10.0 were documented in the Known Issues section of Upgrade Notes and we provided patches for those affected. All the critical issues related to upgrade are now fixed in this 10.0.1 update. There are a lot of other fixes as well.

All the bugfix 10.0.x releases use the same data format and require a license covering 10.0 release date (21 July 2016), so you can upgrade and downgrade the server within 10.0.x releases freely.

Time to download 10.0.1 build 41078 and upgrade.

Happy building!

Posted in Bugfix, Release | Comments Off on TeamCity 10.0.1 Update

Webinar recording: What’s New in TeamCity 10.0

The recording of our July 28 webinar, What’s New in TeamCity 10.0, is now available on the JetBrains YouTube channel.

In this webinar Wes Higbee goes over new and exciting features of the latest TeamCity release, TeamCity 10.0. He demonstrates creating projects and build configurations using TeamCity DSL; setting up a second node for handling running builds data; advancements in integrations with VCS; flaky test detection, and other new features of TeamCity.

Below is the precise timeline of the webinar and select Q&A:

Continue reading

Posted in Features, Partner, Webinar | Comments Off on Webinar recording: What’s New in TeamCity 10.0

What’s New in TeamCity 10, July 28th Webinar

Join us Thursday, July 28th, 10:00 AM – 11:00 AM EDT (16:00 – 17:00 CEST) for our free live webinar, What’s New in TeamCity 10 with Wes Higbee.

In this webinar, Wes will go over some of the new and exciting features of TeamCity 10.0. He will demonstrate creating projects and build configurations using TeamCity DSL; setting up a second node for handling running builds data; advancements in integrations with VCS; flaky test detection, and other new features of TeamCity.

Space is limited, please register now. There will be an opportunity to ask questions during the webinar.

About the presenter:

Wes McClureWes Higbee is passionate about helping companies achieve remarkable results with technology and software. He’s had extensive experience developing software and working with teams to improve how software is developed to meet business objectives. Wes launched Full City Tech to leverage his expertise to help companies rapidly deliver high quality software to delight customers. He has a strong background in using Continuous Integration with TeamCity to bring quality to the table.
Posted in Features, Partner, Webinar | Comments Off on What’s New in TeamCity 10, July 28th Webinar

Ten Years After: Welcome TeamCity 10!

Greetings, everyone!

Our team is excited to announce the arrival of TeamCity 10.0, the jubilee version of our continuous integration and deployment server!

The number ten is regarded as the most perfect of numbers, as it contains the life and the nothing, the Unit that did it all, and the zero, symbol of the matter and the Chaos, of which all came out; it represents a new beginning at a higher level.


We literally follow the symbolism: TeamCity 1.0 saw the light in 2006, and 10 years (and BTW over 16 000 bugfixes!) later, TeamCity 10.0 is here! This TeamCity version comes with advanced features revolutionizing the way you create your projects and builds, making you TeamCity installation more scalable, expanding your horizons with new and improved integrations, all packed in the revised UI.

While so many of our users love the simplicity and ease of configuring projects and builds via the UI, for repetitive tasks like copying projects, build configurations, etc. the programmatic approach is by far more efficient. With TeamCity 10.0 Kotlin-based DSL you’ll enter a new world of creating and maintaining your build infrastructure, dynamically applying all your changes to the projects and builds, skipping the need to use the UI.

In this release another take on scalability has been made – now you can set up a two-node TeamCity, distributing the workload between two servers.

Issue trackers integration has been improved: TFS, GitHub, and Bitbucket are supported out of the box

We’ve made significant progress making VCS-related improvements:
cross-platform support for TFS is finally here; TeamCity works with Perforce streams now and more!

This is just a teaser – for the full list of features see our What’s New  and Release Notes, and download TeamCity 10.0! Remember to check the Upgrade Notes before you install the new version!

Register for our webinar to see the new TeamCity 10.0 features in action!

Happy upgrading and building!

P.S. We’ve also adopted a tradition of giving a decennial retrospective of the TeamCity UI, so take a look at our site to see how pretty our GUI grown to be!

Posted in EAP, Features, FYI, News & Events, Tips&Tricks | 3 Comments

TeamCity 10 RC is out

Greetings, everybody!

This TeamCity 10.0 RC build comes with about 120 bug fixes and feature improvements.

We introduced a dedicated UI to link servers in the new projects popup, reworked the two-node configuration and made some more changes to further improve TeamCity.

All the details are available in our release notes, so don’t hesitate to download build  41965, try it and report any issues to our forum or the tracker.

Remember that the new version, TeamCity 10.0, modifies the data format, and it is still under development,  so it is recommended to install it on a trial server.

Please note that the TeamCity EAP license is not available for this build.

The official TeamCity 10.0 release is just round the corner – don’t miss it!

Happy building!

Posted in Bugfix, EAP, FYI, News & Events, Uncategorized | Comments Off on TeamCity 10 RC is out

TeamCity 10 EAP3 is released

Greeting, everyone!

The impatiently awaited TeamCity 10.0 EAP3 is here  and it comes with a bunch of new really amazing features!

For starters, here are a few of them:

  • Managing the workload for large TeamCity installations can be made more efficient with the 2-node TeamCity server configuration
  • If you tried generating projects programmatically with our DSL, introduced in the previous EAP, you can further take advantage of its improved capabilities.
  • TeamCity has now learned to detect flaky tests and provides you with informative dedicated UI
  • TFS Work Items Tracking support and much more!

All the details are available in our release notes: read them and see for yourself that with all the new features and over 250 bugfixes, this EAP release is impossible to miss!

Besides, this is the last EAP version before TeamCity 10 official release, so your feedback is appreciated more than ever! Please download build 41843, give it a try, and share your opinion on our forum or report any bugs directly to the tracker.

Remember that TeamCity 10.0 is still under development and, like any new version, it changes the data format, so we strongly recommend it be installed on a trial server.

TeamCity 10.0 release is on its way, so keep track of our news!

Happy building!

Posted in Bugfix, EAP, Features, News & Events | 2 Comments

Bica Studios Case Study

This guest post is brought to you by Bica Studios engineering team. It was initially set up as an interview, but it has outgrown the format to become a stand-alone blog post.

What does your company do?


BICA STUDIOS is a team that crafts the best gaming entertainment to bring enduring and inspiring new brands.

We develop great games as a service through a free-to-play approach, allowing millions of players to access new interactive experiences, exciting worlds and know charismatic characters with no initial monetary barriers. Our mission is to make a stand on the entertainment market by exploring current and alternative revenue models.

What obstacles or opportunities was your organization faced with?

From a business point of view, the company has to deal with market saturation and high UA costs. Another strong concern was the validation of proper use of strong engagement mechanics alongside meaningful and inspiring content.

As far as technology, our main concern is being able to deal with and react to change as quickly as possible.

What was your experience like before TC?

Our building pipeline is a complex one.

Having a mobile game as our main product, we obviously target all platforms: iOS, Android and Windows Phone. On the Android platform we target 3 different stores: Google Play Store, Amazon and Aptoide. Each build has a debug and store version.

So: 1 game, 3 platforms, 5 different builds, 10 different setups.

With manual specific configurations for every step, you can guess the amount of time that we take to handle this process and why we call it a ‘release day’ instead of ‘release morning’ or ‘release hour.’

Enter Unity 5 and build setup configuration through editor scripts. Several manual steps could be coded and automated on the build process, reducing a lot of human errors and saving a little bit of time. However, build time was still enormous and demanded at least one full-time dedicated individual to handle.

We decided it was time to a look into the world of Continuous Integration and try to lift the burden of building the project off our development team.

Continue reading

Posted in Blogroll, Case study, FYI | 4 Comments

TeamCity on Docker Hub – it’s official now!

As the popularity of Docker is growing exponentially, Docker Hub has become a huge software distribution platform. Users publish their own images, companies start their official repositories, and everyone is happy.

Up until now JetBrains wasn’t part of this. Then we noticed over 300 images related to TeamCity server, created by enthusiastic Docker Hub users. We decided to join the club and make support for this platform official.

We’ve published the latest version of our software as ready-to-use images and we are going to keep them updated as soon as new versions appear.

There are currently three official TeamCity images in Docker Hub:
1. jetbrains/teamcity-server
Use this image to run a fully functional, ready-to-use TeamCity server. There are multiple options and additional parameters available, which are summarized in the image description on its Docker Hub page.

Once the server is running, you will definitely need some build agents to do the actual work (building) for you. We’ve prepared two separate images for that.

2. jetbrains/teamcity-agent
This image is recommended for general Java development. Build agents created from this image will support agent-side checkout for Git, Mercurial, and SVN, any Java-related activity (as we provide OpenJDK installed), and a full set of features related to Java development.

3. jetbrains/teamcity-minimal-agent
As the requirements for build agents vary considerably, we have also created this minimalistic agent image which you can use for simple builds or as a base for your own images.

Take a look at the official JetBrains Docker Hub page for more details about our Docker images. Give them a try and let us know what you think!

Posted in Blogroll, FYI, How-To's | 12 Comments

TeamCity Digest #7

teamcity-digestWe are glad to present our seventh compilation of recent TeamCity-related articles and blog posts to you and we hope you will enjoy it. If you yourself stumble upon something interesting on the topic, or create your own piece on using TeamCity, please make sure to share it with us.

Darren Guy documents his experience setting up an automated build and deployment solution for Sitecore in a series of posts. Parts 1 and 6 focus specifically on TeamCity, other parts are linked to from each of these posts:
Building a Continuous Integration Environment for Sitecore Part 1 – Teamcity
Building a Continuous Integration Environment for Sitecore Part 6 – TeamCity project

Robert Firek from Codurance has put together this guide for creating a (somewhat simplified) continuous deployment pipeline based on Docker and TeamCity: Docker Meets Continuous Deployment.

Raygun’s Chief of Engineering describes their Continuous deployment process which lets them deploy 6 times per day. To achieve this, they use TeamCity and Octopus Deploy, among some other tools: Continuous Deployment: How To Make It Safer.

Visual Studio Team Services has released an update which can now consume TeamCity builds as artifacts in Release Management:

These two articles describe a Rails project continuous integration environment using TeamCity and Bitbucket. A curious note: the author focuses on using the default free edition of TeamCity which provides 20 build configurations and 3 build agents:
Deploy Your Rails Continuous Integration Environment With TeamCity and BitBucket (Part I: Initial Setup)
Deploy Your Rails Continuous Integration Environment With TeamCity and Bitbucket (Part II: Rails Integration)

Read this short post if you would like to avoid deployment on weekends and configure date/time triggers defined by a CRON expression in TeamCity accordingly: Run Web Application Deployment in TeamCity – Only on Weekdays.

See all TeamCity Digests.

Posted in Digest | Comments Off on TeamCity Digest #7