TeamCity 8.0 (code name Gaya) EAP is open
Hello everyone! Today we’re opening EAP for TeamCity 8.0 (code name Gaya) in order to give you some fresh stuff, to play with during weekend. ;)
Let me briefly describe what we’ve done already and share some of our plans for TeamCity 8.0 (we expect it to be released in Spring 2013).
The major feature of TeamCity 8.0 is sub projects, or project groups (see TW-705, yes, a rather old and rather popular request). We hope it will make TeamCity more scalable in terms of information presentation and the notion of project in TeamCity will become a better match to a real life project (what we call a project right now is rather a VCS branch). While moving in this direction in this EAP we’ve changed how project configuration files are stored on the disk and introduced “root project” (a parent for all of the projects in the system), read more.
Another important feature which we’d like to address in 8.0 is import/export of projects and build configurations (TW-4124). It can become really handy for those who have to maintain several TeamCity instances. At first we plan to provide editable IDs for a project, build configuration, template and VCS root. This will allow assigning IDs on one server so that they do not intersect with IDs on another one, thus will simplify moving configuration files among servers. In this EAP we’ve made the first step in this direction — editable project IDs.
We’ve heard complaints from our customers about the cleanup process. Highly loaded TeamCity server can produce thousands of builds and gigabytes of data each day. Not all of this data will be used in the future, and there is an ability to configure cleanup rules to remove garbage from disks and from the database. Unfortunately, not only this operation takes significant time but web interface becomes inaccessible while the cleanup is in progress. In this EAP we’ve made several improvements in this area, read more and let us know how it works for you.
Mixed mode authentication is the last important addition in the first TeamCity 8.0 EAP. It simplifies migration from one authentication scheme to another by allowing usage of more than one authentication module at a time, read more.
There is also a couple of IDE integration features (currently only available in IntelliJ IDEA plugin). These are: already mentioned some time ago remote debug on agent and showing of test status (success, fail, muted, investigated) right in the editor, plus some other smaller improvements.
Subscribe to Blog updates
TeamCity 2021.2 RC is here
The Release Candidate build for TeamCity 2021.2 is ready! This RC is the last step of our Early Access Program before the upcoming release of TeamCity 2021.2. To be the first one to explore its new features, you can download the RC build and install it on your trial server. Reporting build…
TeamCity 2021.2 EAP3 is here
The third build of TeamCity 2021.2 Early Access Program is available for download! TeamCity 2021.2 EAP3 brings over 70 improvements and fixes. In these release notes, we describe its most prominent new features. Two-factor authentication TeamCity now supports two-factor user authenticat…
TeamCity 2021.2 EAP2 is here
The second build of TeamCity 2021.2 Early Access Program is available for download! TeamCity 2021.2 EAP2 brings over 60 improvements and fixes. In these release notes, we describe its most prominent new features. OAuth 2.0 authentication in Azure DevOps Services Since this EAP, TeamCity…
TeamCity 2021.2 EAP is open
The Early Access Program for TeamCity 2021.2 is open! TeamCity 2021.2 EAP1 brings over 30 improvements and fixes. In these release notes, we describe its most prominent new features. C# Script Runner The new C# Script runner offers a handy way to automate your service tasks in C#: prepa…