TeamCity 7.0: Control the power!
Today we proudly present you TeamCity 7.0, it’s here, it’s ready for you to download. In this release we’ve been focusing on the whole range of aspects that are vital for clear, smooth and controlled continuous integration and modern build management.
The key new features introduced in TeamCity 7 include:
- Build agent pools: Forget those days when there were no agents available for your project because all of them were occupied by builds from other projects. Get hold of your own set of agents: just for your project!
- Typed parameters: Present build parameters clearer in Run Custom Build dialog – use check boxes, selection, field controls with descriptions and validation to make sure those who launch custom build have the right idea of what kind of parameters they change. Safely add password field to this dialog: its value will be kept secret and will never appear in any TeamCity files, such as logs, in unscrambled form.
- Build Chains: It doesn’t matter whether you call it a “pipeline” or a chain, the general idea is almost the same and it gained a lot of interest lately. Four years ago TeamCity first introduced build chains and they have come a long way of improvements since then, most importantly you can now take a closer look at the chains in your project – all spread before your eyes.
- Build failure conditions: All tests pass, but the resulting build is twice bigger then the last successful? Or almost not covered by tests? Or has a shameful load of duplicates? Now you have a way to nip these situations in the bud: just tell TeamCity how “good” you want your builds to be, and it’ll mark those not fitting the condition as failed.
- Incremental builds: Following best software development practices, like keeping your modules as independent as possible, can sometimes give you unexpected new benefits. In this case we’re talking about faster builds. Why run all tests in the whole project when we can get the same result by running only tests affected by a change and take the result of building the rest of the modules from previous build?
- REST API: A long-standing feature request to allow build configuration editing via REST has finally been implemented. Now you can get complete settings of a build configuration or template via REST and change them as you need. Moreover you can create and delete build configurations, as well as projects and VCS roots.
- NuGet: Not only TeamCity can build NuGet packages, install them, or publish to whatever feed you want, it can also be a NuGet server itself!
- ReSharper Inspections: Famous ReSharper Inspections are now available on the server side too. Dead code has no chance to slip in unnoticed.
- and more…
Subscribe to Blog updates
Thanks, we've got you!
CVE-2023-42793 Vulnerability in TeamCity: Post-Mortem
In this post, we describe the actions taken by the TeamCity team after the critical CVE-2023-42793 vulnerability was discovered.
Critical Security Issue Affecting TeamCity On-Premises – Update to 2023.05.4 Now
A critical security issue was recently identified in TeamCity On-Premises. Please upgrade to 2023.05.4 now.
How Gradle Uses TeamCity to Run 30,000 Green Builds Per Day
In this case study, we’ll take a deep look into how Gradle Build Tool uses TeamCity to run tens of thousands of builds a day, while keeping the failure rate under control.