Inside TeamCity with Daniel Gallo
π Secrets and parameters
Part 5: CI/CD is only as good as its config
Pipeline behavior is defined by configuration.
This section covers repositories, project parameters, shared settings, secret management, password parameters, and external secret providers like HashiCorp Vault.
Check the full video:
https://t.co/ohCmBmttYW
#TeamCity #CICD #DevOps #teamcitywithdaniel
Inside TeamCity with Daniel Gallo
βοΈ Cloud agents
Part 4: Where does your build actually run?
Every CI/CD pipeline needs an execution layer.
This part explains TeamCity build agents, cloud execution, terminal debugging, and how the pipeline deploys applications to AWS environments.
Check the full video:
https://t.co/ohCmBmttYW
#TeamCity #CICD #DevOps #teamcitywithdaniel
Start builds, tail logs, and manage agents and queues β without switching windows.
TeamCity CLI is a lightweight, open-source tool that puts TeamCity at your fingertips.
πΏ Watch the new demo of what the CLI can do with its creator @tiulpin π https://t.co/oBcb6ygdDc
5/5
π¬ Small CI/CD question β¬οΈ
In long-running builds, does your team usually wait until the full build finishes to access artifacts?
Or do you publish intermediate outputs earlier?
Curious how teams handle this in practice.
4/5
β οΈ When to use it:
publish-artifacts is most useful when early access to generated files actually matters.
For example:
β‘οΈ long test suites
β‘οΈ large package builds
β‘οΈ generated reports
β‘οΈ intermediate build outputs
It is not something every build needs by default.
Inside TeamCity with Daniel Gallo
π¦ Artifacts
π Build monitoring
Part 3: A build is more than pass or fail
Builds generate more than just a green checkmark.
This clip covers logs, artifacts, parameters, deployment links, and TeamCity performance monitoring including CPU, memory, and disk usage during the build itself.
Check the full video:
https://t.co/ohCmBmttYW
#TeamCity #CICD #DevOps #teamcitywithdaniel
Inside TeamCity with Daniel Gallo
π‘οΈ Quality gate
Part 2: Catch bad code before deploy
Your pipeline should catch issues before users do.
In this part, TeamCity runs Qodana static analysis and collects test results before the build moves further. Vulnerabilities, licensing issues, failed tests, and code quality problems become visible early in the workflow.
Check the full video:
https://t.co/ohCmBmttYW
#TeamCity #CICD #DevOps #teamcitywithdaniel
AI agents can now set up TeamCity build configurations and even full build chains, add build features, and configure parameters.
We ran a couple of experiments to see how far this can go in practice.
Learn more π https://t.co/w4drkAKYkE
Inside TeamCity with Daniel Gallo
βοΈ End-to-end CI/CD
Part 1: CI/CD without the buzzwords
A real pipeline from code to AWS.
This walkthrough covers how TeamCity organizes an entire CI/CD workflow, including code analysis, tests, builds, deployment, project structure, and permissions, all connected in a single pipeline view.
#TeamCity #CICD #DevOps #teamcitywithdaniel
Check the full video:
https://t.co/ohCmBmttYW
Your CI/CD workflow just moved closer to the terminal. β¨οΈ
With the new TeamCity CLI, you can investigate failures, retrigger builds, configure pipelines, and follow logs in real time β without leaving the command line.
Available in TeamCity 2026.1.
https://t.co/dSILZ6fM1k
Hi John!
You can disable the AI Assistant in the Administration > Server Administration: AI Assistant, and then click Disable.
If your question is related to the CLI tools, you authenticate the CLI yourself, so in won't be able to do more than you allowed it to do. For instance, you can generate a read-only access token and give it to the CLI.
Please let me know if you have any further questions.
-Olga
TeamCity 2026.1 is here. π
This release brings CI/CD closer to the way teams work today:
β TeamCity CLI
β MCP support for AI agents
β Pipelines enhancements
β AI Assistant in Enterprise trials
β Bundled SAML authentication
Less context-switching. More control. Faster feedback.
Read whatβs new:
https://t.co/mlw4nxtAXM
Getting ready for today's livestream! π₯
We'll cover what's new in TeamCity 2026.1 and talk about what's coming later this year.
Join us live at 6PM CEST today π https://t.co/7knUvHZR6i
π¨ High-severity security issue affecting TeamCity On-Premises
Weβve identified a high-severity post-authentication vulnerability (CVE-2026-44413) affecting all TeamCity On-Premises versions. TeamCity Cloud is NOT affected.
We strongly recommend upgrading to TeamCity 2026.1 or installing the security patch plugin for 2017.1+ immediately.
More details on our blog: https://t.co/HFSanZuURW
AI is changing how teams build, test, and ship software;
CI/CD needs to evolve, too.
Join our upcoming livestream for a deep dive into TeamCity 2026.1 π
Weβll cover:
π΅ The new TeamCity CLI with Agent Skills
π΅ MCP integration for AI agents
π΅ UI updates for TeamCity Pipelines
π May 12 at 6:00 PM CEST
Register now π
https://t.co/6Bi3UPMrVL