We are happy to announce that we’re building TeamCity Cloud – a CI/CD service that will be completely hosted and supervised by JetBrains. If you’re interested in participating in the beta, please fill out the form on the TeamCity Cloud page. We will add your email to the beta list, and get in touch with you early next year.
Update from July 9, 2020: We have just launched the public beta of TeamCity Cloud. The links above have been updated.
The first bugfix update for our recently released version is ready for download.
Version 2019.2.1 resolves over 120 issues and improves TeamCity security and performance. Besides, this release extends Kotlin DSL implementation by supporting authentication and mirroring in Maven settings which allows accessing custom libraries in private Maven repositories. The full list of addressed problems is available in our release notes.
We strongly recommend upgrading as this TeamCity version resolves several security problems.
Like any bugfix update, 2019.2.1 has the same data format as all 2019.2.x versions, which allows you to easily upgrade/downgrade within these builds.
To upgrade, use one of the following options:
Your feedback is welcome in our forum or tracker.
Happy building!
TeamCity 2019.2.2 bugfix update is here!
This release addresses over 60 issues and improves TeamCity performance. It also resolves a couple of security problems, so upgrade is strongly recommended.
This build also fixes compatibility issues with recent versions of Java 8 (update 242 or later). New UI has got a performance boost in this build as well, especially the build overview page.
The full list of fixes is available in our Release Notes.
As any bugfix update, 2019.2.2 shares the same data format with all the 2019.2.x releases, so you can easily upgrade/downgrade TeamCity within these versions without performing a lengthy backup/restore procedure.
Remember to check our Upgrade Notes and use one of these options to upgrade:
Your feedback is welcome in our forum or tracker.
Happy building!
Today we are opening the Early Access Preview for TeamCity 2020.1!
Traditionally, we named our new release after an Indian city – this time it is a beautiful ancient town of Lakhnau famous for being a many-sided industrial and cultural hub.
Here is what we present in the first EAP:
Read more about these features and see the full list of over 40 improvements and bug fixes in our release notes.
Download Lakhnau 2020.1 EAP1 or pull the Docker image with the eap tag. Remember to install it on a trial server as the new version changes the TeamCity data format and downgrading to the previous production version is not supported.
All our EAP releases come with a 60-day Enterprise evaluation license for an unlimited number of agents and build configurations.
You are welcome to try out the preview build and share your feedback in our forum or issue tracker.
Happy building!
Our work on the new major version comes to its equator, and today we are presenting the second Early Access Program build for TeamCity 2020.1.
TeamCity Lakhnau 2020.1 EAP2 addresses over 50 issues. See the full list of fixes and features in our release notes.
Remember that the new release changes the TeamCity data format and downgrading to the previous production version is not supported. We recommend installing this EAP version on a trial server. If you installed the previous TeamCity EAP version, you can easily upgrade with our automatic update. In other cases, you can download the EAP build or pull the Docker image with the eap tag.
As with any EAP version, this one comes with a 60-day Enterprise evaluation license for an unlimited number of agents and build configurations.
We encourage you to try the new features and share your feedback with us, on our forum or issue tracker.
Happy building!
We want to share what we’re actively developing or designing, and give you sneak peek of the announcements you can expect to see over the coming year.
Developers must have the power to create great software without having to deal with the pain of installing and maintaining build infrastructure. That’s why we are working on TeamCity Cloud – a fully managed CI/CD solution that will be completely hosted and supervised by JetBrains. It will have everything you love about the original TeamCity, and it will run your builds and tests on dedicated instances in the cloud, fully isolated from other users. For current users, we will provide a way to migrate local installations to the cloud solution.
We are going to launch a public beta of TeamCity Cloud in the summer of 2020.
YouTrack project: https://youtrack.jetbrains.com/issues/TCC.
Developers all over the world love TeamCity’s tight integrations with build tools and external services, and we take great care to support them in the best possible way. Below is a list of the new features that we are planning to add.
Many of our users are excited about Microsoft’s plans to release .NET 5 – a new platform that will unite .NET Core and .NET Framework. .NET 5 will eliminate the differences between developing for different platforms, and we are planning to follow the same path in TeamCity. The all-new .NET build runner will unite all 5 runners that we currently have and allow you to build any type of app, with all available runtime options.
We are not planning to remove the old build runners in the next few releases, but our general goal is to implement new features and bug fixes only in the new one.
TeamCity 2019.2.3 bugfix update is already here.
This release fixes over 130 issues and brings notable performance improvements. We strongly recommend upgrading as this version resolves a few security problems.
The main improvement of this release is the reworked .NET runner functionality. To address the Microsoft vision of the .NET SDK roadmap and ensure the most relevant experience with .NET for our users, we have put all supported .NET commands together in one runner. This universal .NET runner offers the following features:
You can continue using existing .NET steps in the new version – no additional tuning is required. More details on migration from obsolete build steps are available in our documentation.
This release also fixes many issues with the build log in the experimental UI. We encourage you to give the experimental UI a go to benefit from a smoother user experience.
The full list of fixes is available in our release notes.
As any bugfix update, 2019.2.3 shares the data format with other 2019.2.x releases, so you can upgrade/downgrade TeamCity within these versions without performing a backup/restore procedure.
However, we have decided to introduce the new .NET functionality in a bugfix release so you can benefit from the new features as soon as possible. After manually switching to new .NET commands and settings in 2019.2.3, you might encounter compatibility problems if downgrading to an earlier version of TeamCity. Consider backing up the TeamCity data to prevent any issues in this case. Refer to our Upgrade Notes for more information.
Use one of these options to upgrade:
Your feedback is welcome in our forum or tracker.
Happy building!
Our final Early Access Program build for TeamCity 2020.1 is ready.
TeamCity Lakhnau 2020.1 EAP3 brings over 90 new features and bug fixes.
The full list of features is available in our release notes.
Remember that the new release changes the TeamCity data format and downgrading to the previous production version is not supported. We recommend installing this EAP version on a trial server. If you installed the previous TeamCity EAP version, you can easily upgrade with our automatic update. In other cases, you can download the EAP build or pull the Docker image with the eap tag.
As with any EAP version, this one comes with a 60-day Enterprise evaluation license for an unlimited number of agents and build configurations.
We encourage you to try the new features and share your feedback with us, on our forum or issue tracker.
Happy building!
We are eager to present the new TeamCity Notifier extension that allows receiving real-time notifications about build statuses and events directly in your browser.
The extension is available for Mozilla Firefox, Opera, and Google Chrome (including all Chromium-based browsers such as Microsoft Edge).
Main features
Note that Browser Notifier aims at replacing our obsolete Windows Tray Notifier and automatically uses all rules configured for it, if any. The My Settings & Tools | Notification Rules | Windows Tray Notifier tab in TeamCity is renamed to Browser Notifier.
How to enable
Follow these steps to start using the Notifier:
How it works
After detecting an active TeamCity session, the Notifier will be monitoring the server and reporting events in real time similarly to how regular notifications work in your OS and browser:
Click on the notification to get to the related TeamCity build page.
Moreover, you can see the history of TeamCity notifications in your OS notification area. For example, on Windows, click 
in the lower right corner of the screen to access it:
If you are signed into multiple TeamCity servers in the same browser, the extension will be ready to support this case. The Notifier remembers each detected session and automatically disables/enables notifications for it when you – respectively – sign off/into this server. You can manage all sessions after clicking the Notifier icon or in its Options.
Try out the new extension and leave your feedback on our forum or issue tracker.
Happy building!
TeamCity 2019.2.4 bugfix update is available.
This release brings over 30 improvements. Most notable fixes are:
us-east-1 AWS region in S3 artifact storage settings.The full list of fixes is available in our release notes.
As any bugfix update, 2019.2.4 shares the data format with other 2019.2.x releases, so you can upgrade/downgrade TeamCity within these versions without performing a backup/restore procedure.
Use one of the following options to upgrade:
Your feedback is welcome in our forum or tracker.
Happy building!
Today we are presenting our release candidate build for TeamCity 2020.1.
This build contains over 100 features and bug fixes.
The full list of features is available in our release notes.
Remember that the new release changes the TeamCity data format and downgrading to the previous production version is not supported. We recommend installing this EAP version on a trial server. If you installed the previous TeamCity EAP version, you can easily upgrade with our automatic update. In other cases, you can download the EAP build or pull the Docker image with the eap tag.
The TeamCity RC builds come without the EAP license but the license for the 2020.1 EAP 3 release is valid for this RC.
Your feedback is always welcome in our forum or tracker.
Stay tuned for the upcoming news on our 2020.1 release build.
Happy building!
TeamCity 2020.1 features conditional build steps, allows launching build agents in a Kubernetes cluster, and integrates with Azure DevOps and Jira Software Cloud. It adds more capabilities to secondary servers in a multi-node setup, comes with a new Slack notifier, and has many great improvements to the experimental UI.
The first bugfix update for TeamCity 2020.1 is ready for download.
Version 2020.1.1 resolves over 120 issues. Among the bug fixes, it introduces several important updates such as:
linux-sudo. The linux-sudo image is most convenient for running Docker within Docker and installing additional software during the build.The full list of fixes is available in our release notes.
We strongly recommend upgrading as this TeamCity version provides security and performance improvements.
Like any bugfix update, 2020.1.1 has the same data format as all 2020.1.x versions, which allows you to easily upgrade/downgrade within these builds.
Remember to check the upgrade notes and use one of the following options to upgrade:
Your feedback is welcome in our forum or tracker.
Happy building!
Developing a working piece of software is difficult. Just like building an airplane, it requires talented people, working components, and a testing framework. No plane leaves the hangar before everything is ready, checked and double-checked.
In JetBrains, we adopt the same philosophy for building our software. Vigorous testing helps us discover bugs and problems before the final product takes off. Just like building a plane, software development is a process that consists of multiple stages. Although the authors of this post are not aerospace engineers, we will use simplified aircraft analogies. There are several reasons for that: aircraft is beautiful, it is pure engineering, and it reveals that the problems we raise here are not exclusive to software engineering.
The bigger your product, the more steps and modules there are. To make sure your software is ready to lift off, every module needs to be tested and correctly integrated with everything else. CI/CD services, if set up correctly, help automate this process. Most importantly, they remove the human factor famous for one careless action being able to lead to total disaster.
Contrary to popular belief, testing is very important in front-end development. To continue the analogy, your plane is not only required to fly – it has to be comfortable inside! Moreover, its exterior affects how airplane flights (aerodynamics). Getting back to the front end, this means that you have to test the usability as well as functionality. This makes front-end testing a must. In this article, we will provide an overview of UI testing used in TeamCity. If you have any questions about the technical details – don’t hesitate to ask us.
In TeamCity 2020.1, we have introduced a highly demanded feature – conditional build steps. With new execution conditions, you can control whether or not a given build step is executed in every build run, depending on the current environment and parameters.
In this video demonstration we:
Here is a quick recap of the video:
To add execution conditions to a build step:
In every build run, this conditional step will only be executed if all its execution conditions are satisfied.
By combining execution conditions with other classic features of TeamCity, you can significantly improve your building experience. One great example is creating a condition that is based on a build parameter.
Let’s consider the following use case:
Your build configuration can be deployed to any of the three environments (QA, Staging, and Production). By default, it is deployed to QA, but you can run a custom build and select a different environment. One of the build steps contains a script that must be executed only when deployed to Production.
With conditional steps, it is easy to arrange:
Now, you can click Deploy to run a custom build. Since you selected the Prompt display type for the parameter, TeamCity will ask you about the target environment for this build.
If you select anything other than Production, the production-only build step will be skipped in this custom build run:
That’s it for the tutorial!
Refer to our documentation for more information and leave your feedback about the feature in the comments.
Happy building!
TeamCity 2020.1.2 bugfix update is already here.
This release addresses over 50 issues and enhancements, including:
We strongly recommend upgrading as this version resolves several security and performance problems.
The full list of fixes is available in our release notes.
As any bugfix update, 2020.1.2 shares the same data format with all the 2020.1.x releases, so you can easily upgrade/downgrade TeamCity within these versions without performing a backup/restore procedure.
Remember to check our upgrade notes and use one of these options to upgrade:
Your feedback is welcome in our forum or tracker.
Happy building!
Today we launch the public beta of TeamCity Cloud, a product that we’ve been busy working on in recent months. TeamCity Cloud is a managed CI/CD service designed for teams that don’t want to deal with running and scaling their own build servers, but at the same time have demanding requirements for availability and security of their DevOps pipelines.
This release was made possible not only by the hard work of several teams inside JetBrains, but also by private beta users who helped us eradicate bugs and provided invaluable feedback. We are tremendously grateful for their participation and support!
In TeamCity 2020.1, we have introduced a highly demanded feature – conditional build steps. With new execution conditions, you can control whether or not a given build step is executed in every build run, depending on the current environment and parameters.
In this video demonstration we:
Here is a quick recap of the video:
To add execution conditions to a build step:
In every build run, this conditional step will only be executed if all its execution conditions are satisfied.
By combining execution conditions with other classic features of TeamCity, you can significantly improve your building experience. One great example is creating a condition that is based on a build parameter.
Let’s consider the following use case:
Your build configuration can be deployed to any of the three environments (QA, Staging, and Production). By default, it is deployed to QA, but you can run a custom build and select a different environment. One of the build steps contains a script that must be executed only when deployed to Production.
With conditional steps, it is easy to arrange:
Now, you can click Deploy to run a custom build. Since you selected the Prompt display type for the parameter, TeamCity will ask you about the target environment for this build.
If you select anything other than Production, the production-only build step will be skipped in this custom build run:
That’s it for the tutorial!
Refer to our documentation for more information and leave your feedback about the feature in the comments.
Happy building!
TeamCity 2020.1.2 bugfix update is already here.
This release addresses over 50 issues and enhancements, including:
We strongly recommend upgrading as this version resolves several security and performance problems.
The full list of fixes is available in our release notes.
As any bugfix update, 2020.1.2 shares the same data format with all the 2020.1.x releases, so you can easily upgrade/downgrade TeamCity within these versions without performing a backup/restore procedure.
Remember to check our upgrade notes and use one of these options to upgrade:
Your feedback is welcome in our forum or tracker.
Happy building!