
Powerful CI/CD solution by @JetBrains, the creators of IntelliJ IDEA, ReSharper, Kotlin, and many other great tools for developers and teams
Joined March 2008
- Tweets2.6K
- Following20
- Followers9.1K
- Likes465
Your pipelines may be getting slower even when builds are passing.
Are jobs spending more time in the queue?
Are tests taking longer?
Is one stage holding up the rest?
Here’s what to measure and which tools can help 👉 jb.gg/5lmdhu
Built-in dashboards, #Prometheus and #Grafana, logs, traces: where should you start with CI/CD observability?
In our article, we look at each approach and discuss how to choose the right setup for your team 👉 jb.gg/5lmdhu
A failed build tells you something broke.
Queue time, build duration, and test trends can help you see the pattern behind it.
Our guide covers the metrics and tools that help teams understand their CI/CD pipelines: jb.gg/5lmdhu
1/4
You can't consolidate away a client requirement.
Before retiring a CI/CD tool, find out which customer's work still depends on it.
3/4
For each tool marked for retirement, write down who needs it and what requirement it meets. Then find out who can agree to a change.
4/4
A migration plan needs an answer for that work before it needs a shutdown date.
Which external requirement has kept a CI/CD tool in your stack?
Full report:
jb.gg/6gnj9q
Less waiting for agents. Faster feedback on your code.
Meet Warm Agents for TeamCity: keep cloud agents running and ready for incoming builds, reducing delays caused by instance startup.
See how it works:
blog.jetbrains.com/teamcity/…
The State of CI/CD Report 2026 is out! 🎉
This year, we gathered information from four different studies, combining responses from 35K+ participants.
See what’s trending in the world of CI/CD 👉 jb.gg/state-of-cicd
You can now mirror real Jenkins jobs in TeamCity – without migration.
Install the Jenkins Bridge plugin and connect Jenkins to explore build results in TeamCity.
The plugin is experimental, and we'd love your feedback: plugins.jetbrains.com/plugin…
1/5
How do you take a Kotlin Multiplatform app from its first Git push to TestFlight?
We designed the TeamCity integration around three steps: build and test, publish, and then automate.
Here’s how that shaped the experience. 🧵
4/5
Ask for what’s needed, when it’s needed.
Once the build passes, a single form collects Apple signing details for TestFlight publishing.
Connecting GitHub comes next, turning future pushes into automated builds, tests, signing, and uploads.
5/5
Around 10 usability sessions with KMP developers helped us validate the guided flow and uncover friction before release.
Read the story behind the design of the Kotlin Multiplatform + TeamCity integration:
jb.gg/KotlinMultiplatform
20 years of keeping builds green. 💚
TeamCity turns 20 today! To everyone who’s built with us, trusted us, and helped shape TeamCity along the way: thank you.
Meet the team behind the builds. 🎬
JetBrains TeamCity retweeted
We've reimagined JetBrains IDEs to become the ultimate agentic workbench.
Air is an open hub for agents inside your IDE:
-Any agents to run (Claude, Codex & many more)
-Agents are more efficient with IDE intelligence
-Free Junie Lite agent bundled
-Cloud runs via Air Teams
⬇️
🔑 Key rotation is the chore everyone postpones because it breaks things mid-flight.
The OIDC JWT plugin rotates signing keys from the UI or an authorized HTTP endpoint. Running builds keep running, and previously issued tokens stay valid by default.
A rotation that costs nothing is a rotation that actually happens on schedule.








