r/teamcity • • Feb 13 '26

Our internal TeamCity server just hit 10,000 simultaneous build agents

14 Upvotes

Just wanted to share a milestone from our internal setup at JetBrains: we’ve crossed 10,000 build agents running simultaneously on a single TeamCity server.

At JetBrains, we build everything with TeamCity - from plugins and libraries to IDEs to the Kotlin programming language and TeamCity itself.

One more thing that might be interesting - we update our internal TeamCity server daily. Every new build is deployed to our own production first, so new features, bug fixes, and performance improvements are tested at real production scale before they ever reach a public release.


r/teamcity • • Mar 19 '26

Introducing TeamCity CLI

12 Upvotes

A CLI for TeamCity has been a long-standing request from the community. Here’s how it works and what you can use it for.

Learn more from the article: https://blog.jetbrains.com/teamcity/2026/03/teamcity-cli/


r/teamcity • • Jan 26 '26

TeamCity from the terminal - early CLI experiment, looking for feedback

12 Upvotes

Leaving the terminal every time you need to check a build status or trigger a run or fetch logs is not cool - so we've built the first version of the CLI that currently covers this basic stuff.

It’s very much a first iteration. There are plenty of directions this could go next (more automation, admin tasks, etc.), so before taking it further we’d love feedback from actual TeamCity users.

Repo: https://github.com/JetBrains/teamcity-cli


r/teamcity • • May 20 '26

Introducing TeamCity 2026.1

9 Upvotes

TeamCity 2026.1 is out and packed with helpful features. We’re introducing the TeamCity CLI and MCP support, as well as Pipelines enhancements to make configuring TeamCity more convenient and powerful. As of this release, AI Assistant is available in Enterprise trial accounts, and the SAML authentication plugin comes bundled with TeamCity.

Read the blog for more information: https://blog.jetbrains.com/teamcity/2026/05/teamcity-20261/


r/teamcity • • Mar 02 '26

TeamCity redesign part 2: project creation

8 Upvotes

TeamCity's project creation flow is about to change. For an (almost!) 20 yo product, one can imagine the layers of UI history underneath and the size of the task. It used to take 20+ clicks to create a project, and many advanced features were hidden. That will change soon https://blog.jetbrains.com/teamcity/2026/02/introducing-teamcitys-new-design-phase-2/


r/teamcity • • Sep 25 '26

How We Designed the Kotlin Multiplatform and TeamCity Integration

7 Upvotes

Recently, we designed and built the new TeamCity integration for Kotlin Multiplatform. Now, you can publish the iOS app straight from your IDE.

Learn more about the integration and how we designed it in our blog post.


r/teamcity • • Jul 13 '26

What’s your most slept-on TeamCity feature? Here are four of mine

7 Upvotes

Been in TeamCity a while and keep running into features that quietly do a ton of work but rarely get talked about. Four I’d put on the “slept-on” list, curious which ones you swear by, and what I’m missing.

  1. Per-build resource graphs (PerfMon tab). Every build records agent CPU, disk I/O, and memory automatically now, so you can catch a build that’s secretly disk-I/O bound instead of guessing at agent specs.

  2. Build reuse via snapshot dependencies. Same source snapshot across the whole chain, and a step whose sources didn’t change gets reused instead of re-run. Add checkout rules, and only the changed part runs.

  3. Deployment-type configs. Flip a config from Regular to Deployment, and you get Deploy/Redeploy, a Deployments view, and a per-change tab that tells you what’s in prod and when it shipped.

  4. Failure conditions beyond pass/fail. Fail a build if coverage drops vs the last successful build, if artifact size balloons, or if duration regresses. The coverage ratchet is my favorite: “don’t make it worse” beats mandating a fixed %.

What’s your most underused TeamCity feature, the one you’d tell a new user to turn on immediately? And is there a slick use of build chains, templates, or Kotlin DSL I should be stealing?


r/teamcity • • Jun 11 '26

A bit of CI/CD humor 😅

Post image
7 Upvotes

r/teamcity • • Jun 02 '26

Brave’s DevOps team: “We can assume things will work and won’t randomly break.”

7 Upvotes

That line from Brave’s TeamCity case study feels like the real story.

Brave moved browser PR builds to TeamCity after dealing with an unreliable CI system, unfixed bugs, unmaintained plugins, and too many custom workarounds.

The technical setup is worth reading:

  • PR builds moved to TeamCity platform by platform

  • Configuration managed entirely in Kotlin DSL

  • Changes reviewed through pull requests and automated checks

  • Ephemeral EC2 agents provisioned with TeamCity cloud profiles

  • Persistent workspace volumes used for incremental builds

  • REST API orchestration used to fan out downstream builds dynamically

It is a good example of TeamCity being used not just as a build runner, but as the stable CI/CD layer for a large, multiplatform engineering system.

Full case study: https://www.jetbrains.com/company/customers/experience/brave/

Curious how other teams here structure larger TeamCity setups: do you keep most orchestration inside TeamCity build chains, or do you use the REST API heavily?


r/teamcity • • Sep 08 '26

TeamCity 2026.2 is out! 🎉

6 Upvotes

Pipelines are now generally available, BYOK, new MCP tools, and much more. Read the release blog post to learn more.


r/teamcity • • Jul 16 '26

TeamCity Roadmap 2026

6 Upvotes

The TeamCity roadmap for 2026 has just landed: https://www.jetbrains.com/pages/teamcity-roadmap/

Learn more about what's coming this year.


r/teamcity • • May 11 '26

High-Severity Security Issue Affecting TeamCity On-Premises (CVE-2026-44413) – Update to 2026.1 Now

Thumbnail
blog.jetbrains.com
6 Upvotes

r/teamcity • • Feb 05 '26

The devops job has its moments

Post image
6 Upvotes

r/teamcity • • Oct 07 '26

New experimental TeamCity plugin that mirrors Jenkins jobs

5 Upvotes

The idea behind Jenkins Bridge is simple: Connect TeamCity to Jenkins and mirror your Jenkins jobs in the TeamCity UI without migrating or rewriting them.

In this first version, you can:

  • Start Jenkins jobs from TeamCity, including parameterized builds.

  • Follow live build progress and console output in TeamCity.

  • View Jenkins pipeline stages, dependencies, and stage logs in the Pipeline Graph.

  • Investigate Jenkins test results and failure details using TeamCity’s test interface.

  • See build results, parameters, VCS changes, and published artifacts.

If you use Jenkins, would this be useful in your setup? Feedback from real cases would be terrific.

Thanks a lot!


r/teamcity • • May 26 '26

How AI Agents Can Work with TeamCity

Thumbnail
blog.jetbrains.com
5 Upvotes

TL;DR: At some point, we crossed an interesting threshold. AI agents can now set up TeamCity build configurations and even full build chains, add build features, and configure parameters.

This works because TeamCity documentation is structured and accessible through MCP via Context7, and because agents can rely on tools like the TeamCity CLI and the teamcity-cli skill.

We ran a couple of experiments recently to see how far this can go in practice.


r/teamcity • • May 07 '26

TeamCity recipe of the week

5 Upvotes

This week’s TeamCity tip: unlock faster feedback by making build artifacts available as soon as they’re created with the publish-artifacts recipe, even before the build finishes.

This approach is helpful when:

  • a long build generates logs, reports, or packaged files before completion;

  • Someone needs early access to generated files.

  • another build step or team member requires outputs before the pipeline finishes;

  • You need to provide partial results without waiting for the final build status.

A simple example:

A build takes 40 minutes.
After 10 minutes, it generates reports or packaged files.
Instead of waiting for the build to finish, this recipe publishes those files earlier.

This method does not replace standard artifact publishing in all cases. It is most valuable when early access to outputs is important.

I am collecting practical examples of TeamCity recipes and their applications in real workflows.

Let me know which TeamCity recipe or use case you want to see covered next. Your input directly shapes upcoming tips!

  • Slack notifications

  • AWS CLI

  • XML report import

  • build tagging

  • Node setup

  • something else


r/teamcity • • Apr 29 '26

[Livestream] TeamCity 2026.1: AI, Pipelines, and Enterprise CI/CD Improvements

5 Upvotes

We're soon releasing TeamCity 2026.1! 🎉

The new version comes with a set of great improvements: the TeamCity CLI, MCP for AI Agents, AI Assistant available for Enterprise trial licenses, and much more!

Join us for a live walkthrough of the latest updates, including support for both the Kotlin DSL and YAML in pipelines.

Register here 🔗


r/teamcity • • Oct 23 '24

Automating Godot Game Builds With TeamCity

Thumbnail
blog.jetbrains.com
5 Upvotes

r/teamcity • • May 16 '24

Introducing the Unreal Engine Plugin for TeamCity

Thumbnail
blog.jetbrains.com
5 Upvotes

r/teamcity • • Mar 04 '24

Additional Critical Security Issues Affecting TeamCity On-Premises (CVE-2024-27198 and CVE-2024-27199)

Thumbnail
blog.jetbrains.com
5 Upvotes

r/teamcity • • Jan 06 '21

Teamcity has a potential backdoor

Thumbnail
nytimes.com
5 Upvotes

r/teamcity • • 19h ago

Run AI Agents in TeamCity

Thumbnail
blog.jetbrains.com
4 Upvotes

The new experimental AI Agents plugin for TeamCity lets you run Codex and Claude Code directly in TeamCity builds and connect them to the LLM provider of your choice.

The plugin installs the coding agent on the TeamCity build agent, provides credentials safely for the duration of the build, and collects usage statistics and agent trajectories. Learn more in our recent blog post.


r/teamcity • • Oct 13 '26

State of CI/CD Report 2026

4 Upvotes

The report combines the data from 4 different studies – DevEco and two AI Pulses by u/jetbrains, and State of CI/CD Tools by u/teamcity.

Main takeaways:

  • 30.5% use an on-premises installation, the highest share recorded in five years.

  • 48.8% of organizations use AI for at least one CI/CD task.

  • Only 8% run AI-powered steps directly inside a build or test.

  • 28% interact with their CI/CD tools through MCP or agent skills

Here's the full report: https://jb.gg/state-of-cicd

What's the most surprising finding for you?


r/teamcity • • Aug 13 '26

Five things in the TeamCity hardening docs that are off by default and probably shouldn't be

4 Upvotes

 I went through the Security Notes page properly this week rather than skimming it, and a few things in there are easy to miss. Posting them because the page is long, and most people bounce off it.

1. Super User Access. TeamCity writes a token to teamcity-server.log that allows whoever has it to log in as a system administrator. Please be careful when you've locked yourself out. Less useful if you ship logs to an external system. teamcity.superUser.disable=true in internal properties, then restart.

2. Credential scrambling is not encryption. Passwords for external systems are scrambled with 3DES and a fixed key in the Data Directory. Filesystem or DB access is enough to reverse it. There's a custom encryption key option that actually provides encryption.

3. Build-level auth parameters. Anyone with "View build configuration settings" can read them and use them to reach projects they don't have access to. teamcity.buildAuth.enableStrictMode=true closes it.

4. Empty the database on first start. A server encountering an empty DB grants access to the first person who connects. teamcity.installation.completed=true in conf/teamcity-startup.properties. Mostly relevant when restoring from backup.

5. The Default agent pool. Projects can fall back into Default after reconfiguration, and builds on the same agent are not isolated from each other. A public-PR project landing next to a private one is a real problem. Please just keep the default empty so there's nothing to fall back on.

Full page: https://jb.gg/s6o8oq
There's a short PDF version linked from it if you want something to hand to your team.

Curious which of these people actually has on. I guess that the agent pool one is most commonly missed.