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
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
🚨 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
If you ever wanted to take a look at TeamCity but didn't want to connect your own repos, this is for you.
We set up a demo instance of TeamCity that you can check out without connecting your own data:
👉 https://t.co/zv0TPvWhJu, login as guest.
New course: Spec-Driven Development with Coding Agents, built in partnership with @jetbrains, and taught by @paulweveritt.
Vibe coding is fast, but often produces code that doesn't match what you asked for. This short course teaches you spec-driven development: write a detailed spec defining what to build, and work with your coding agent to implement it. Many of the best developers already build this way.
A spec lets you control large code changes with a few words, preserve context across agent sessions, and stay in control as your project grows in complexity.
Skills you'll gain:
- Write a detailed specification to define your mission, tech stack, and roadmap, giving your agent the context it needs from the start
- Plan, implement, and validate features in iterative loops using a spec as your agent's guide
- Apply the same repeatable workflow to both new and legacy codebases
- Package your workflow into a portable agent skill that works across agents and IDEs
Join and write specs that keep your coding agent on track!
https://t.co/hI4GwuvhtN
I'm looking for work, so if you want an experienced devrel person/leader, if you need a technical educator, or if you want some consulting on how to help your devs work more effectively, ping me.
I used Claude Code + @TeamCity MCP to set up two CI projects from scratch -- entirely from the terminal.
Created two projects, VCS roots with SSH deploy keys, build configs, versioned settings repos — all through the REST API and MCP tools. TeamCity generated the Kotlin DSL and pushed it to GitHub.
The MCP integration lets you query builds, read logs, and configure projects conversationally. The setup that would normally be 30 minutes of clicking through admin UI took one session.
Total: two projects, two settings repos, four deploy keys, versioned Kotlin DSL — all wired up.
#TeamCity #MCP #AIAgents #DevOps
Our technical lead Pavel has reviewed thousands of commits over the years.
That experience helps him spot changes that work technically but don’t fit the project, and suggest better approaches.
The question is: How do we teach AI agents to be like Pavel?
Here's how we taught AI agents to see the bigger picture 👉 https://t.co/6BOWegsK5m
What's interesting about this CLI client - you can actually open a terminal to the remote agent that is running a build (if you have permissions, of course). #teamcity
Introducing TeamCity CLI 🎉
It includes over 60 commands. Use it to investigate a failed build, find the root cause of a problem, or fix and re-trigger.
Read more about how TeamCity CLI can help: https://t.co/q1yVGPRWI2
Unlike standard MCP, where agents are limited to a fixed command set,
MCP Steroid plugin for IntelliJ-based IDEs gives agents programmatic access to the full IDE via Kotlin code — refactoring, debugger, inspections, everything developers love about JetBrains.
The agent writes its own code to work with IntelliJ APIs for each specific task.
Result: 20–54% speedup on benchmarks.
Runs headless — drop it into CI or any agentic pipeline.
🔗 https://t.co/A3Nlmw0jA0
#MCP #AIAgents #JetBrains #IntelliJ #DeveloperTools #AgenticAI #Kotlin #VC #NeedFunding #MCPSteroid
Have you tried Chrome Split View with Checkvist yet?
Open Checkvist in one tab, browse in another, copy, paste, drag-n-drop from web pages to Checkvist.
Do research, organise notes for a blog post, article, you name it. Enjoy!🤓
https://t.co/HEsSVsnWPT
Děkuji všem lidem, kteří i letos dorazili na Staroměstské náměstí ukázat, že stále stojíme za Ukrajinou. A že za ní budeme stát, dokud to bude potřeba.
TeamCity 2025.11 On-Prem just got better 🚀
Two quality-of-life tweaks for the IJ plugin, 13 bug fixes, 8 performance updates, and 5 security fixes.
Grab the latest bug-fix update here: https://t.co/5QT87Vd9Cb
@simongeering@teamcity I'm not entirely get the question, but almost all of the agents fetch sources from Git repositories (with some pre-fetched mirrors sometimes)