Failed main build
Tom Reilly, tech lead at BigCo, asked why the last main build of the web project failed. Memtro read the build's status text and test counts, then listed the failing tests and build problems, marking which were new.
TeamCity + Memtro
Why did the last main build of the web project fail?
TeamCity tells you what your builds are doing, self-hosted or in the cloud. You see builds by configuration, branch, state and status with who triggered them, one build with its test and problem counts, the build queue with wait reasons, configurations, projects, failing tests, build problems and agents. When asked and granted, Memtro can run, cancel or delete builds, comment, tag or pin them, assign investigations, mute tests, enable or disable agents and pause the whole queue. Worth knowing: the server must be reachable over https with a publicly trusted certificate, and pausing the queue needs a server administrator's token.
In Memtro
What you can do with TeamCity in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right TeamCity tool, reads what it needs, and answers with the source cited.
What it does
- 01See builds by configuration, project, branch, state or status, with trigger, agent, tags and times.
- 02Read one build's status text, test counts and problem count, then the failing tests and build problems by name.
- 03Check the build queue with each build's position, wait reason and estimated start.
- 04List build configurations, projects and agents with whether each is connected, enabled and up to date.
- 05When asked and granted, run a build, which can deploy or publish and notifies people per their rules, or cancel or delete one.
- 06When asked and granted, comment, tag or pin builds, assign an investigation, which notifies that person, mute tests, disable agents or pause the queue.
Acts when asked
When you ask it to
These tools change something in TeamCity. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
- 01Run a build of a configuration, optionally on a branch or with parameters
- 02Cancel a queued build
- 03Cancel a running build
- 04Delete a finished build with its artifacts and history (permanent)
- 05Comment on a build
- 06Tag a build
- 07Pin or unpin a build
- 08Assign an investigation of a configuration's problems to a person
- 09Mute a test in a project
- 10Unmute a test
- 11Enable or disable a build agent
- 12Pause or resume the whole build queue
In practice
Ask it like you would a colleague
Once TeamCity is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
TeamCity + Memtro
Why did the last main build of the web project fail?
What is waiting in the build queue, and why?
Which tests are currently failing in the API project?
Which build agents are disconnected?
Run the nightly build of the web project on the release branch.
Pinning a release build
Priya Sharma, release manager at Acme Ltd, asked Memtro to pin and tag the build that went to production. Memtro pinned it so clean-up never deletes it and added the tag, visible to everyone who can see the build.
Teams
Where it fits
The teams that lean on TeamCity most, a question each of them asks, and what they connect beside it.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- Agent buildersMemory and tools for the agents you buildSolo builder, Platform team, Automation engineer, Whoever signs it off“Search memtro for what we know about Acme before drafting the proposal”Used alongside GitHub, Linear and Slack.
Better together
Works with
A record in TeamCity is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
- Work managementTeamCity with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementTeamCity with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementTeamCity with LinearIssues, projects and teams, synced hourly into memory.
- SupportTeamCity with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportTeamCity with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportTeamCity with IntercomCustomer conversations and the people behind them, in your company memory.
- Documents and wikisTeamCity with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisTeamCity with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisTeamCity with ConfluenceSearch and read wiki pages, and write them when you ask.
Also in Engineering and operations
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
- GitHub
- AWS CloudWatch
- Sentry
- ServiceNow
- Okta
- Twilio
- AWS CloudTrail
- GitLab
- Bitbucket
- Vercel
- PagerDuty
- Datadog
- Grafana
- incident.io
- Azure DevOps
- CircleCI
- Cloudflare
- LaunchDarkly
- New Relic
- Rollbar
- Snyk
- Better Stack
- Buildkite
- DigitalOcean
- Heroku
- Netlify
- SonarQube Cloud
- Statuspage
UptimeRobot- Axiom
- BugSnag
- Checkly
- Hetzner Cloud
Honeycomb- Pingdom
- Render
- Statsig
- Sumo Logic
- Supabase
- HCP Terraform
- Vultr
- Airbrake
- Codecov
Cronitor- Dynatrace
FireHydrant- Fly.io
- Honeybadger
- Akamai Linode
- Octopus Deploy
- Pulumi
- Rootly
- Semgrep
- Splunk
StatusCake- Tailscale
- Argo CD
- authentik
- Coolify
- Gitea
GlitchTip
GLPI- Jenkins
Langfuse
LibreNMS- n8n
NetBox- Portainer
- Prefect
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone- OpenAI (usage and cost)
- Anthropic (usage and cost)
- Algolia
- Flagsmith
- Unleash
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert- KnowBe4
JumpCloud
ConfigCat- Railway
- Fastly
- Postman
- Make
- Braintrust
- OpenRouter
- ElevenLabs
Split- Scaleway
Aikido Security- AssemblyAI
Astronomer- Bamboo
- Baseten
- Bitrise
- Bitwarden
- BrowserStack
- bunny.net
- Cachet
- Checkmk
- Civo
- Cloudsmith
- Codacy
- Codemagic
Comet Opik- Coralogix
CrowdStrike Falcon- Dagster+
- DeepSource
Detectify- Docker Hub
Domotz- Grafana OnCall
- Harness
- Hugging Face
- Instatus
- Koyeb
- Lambda Cloud
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary- Mezmo
NinjaOne- Nomad
Northflank- Oh Dear
- OVHcloud
Portkey- Probely (Snyk API & Web)
PromptLayer- Proxmox VE
PRTG Network Monitor- Qase
Raygun
Retell AI- Retool
Runpod- SecurityScorecard
- Semaphore CI
Shodan- SigNoz
- Socket
Spike.sh
Squadcast- SwaggerHub
Tenable- Together AI
- Travis CI
UpGuard
Uptime.com
Vanta- Vapi
- Windmill
Zenduty- OpsLevel
Cortex- Auth0
- Clerk
WorkOS
Kandji
Automox
Huntress- HackerOne
SimpleMDM- AppSignal
Healthchecks.io
Rapid7 InsightVM- 1Password Events
- JFrog Artifactory
- Sauce Labs
Zenhub- Deepgram
- Replicate
Setup
How to connect
Connect withServer URL and Access token
- 1
In TeamCity, open your Profile, then Access Tokens, and create a token. A dedicated user with only the roles Memtro needs is safer.
- 2
In Memtro, open Connections → TeamCity and enter the Server URL, with any context path, and the Access token.
- 3
Viewing is enough for reads. An administrator grants the actions by name, such as Run build or Mute test, to the teams that may use them.
- 4
Ask why the last main build of the web project failed.
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The TeamCity tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in TeamCity?+
Only when you ask, and only what it has been granted: run a build of a configuration, optionally on a branch or with parameters; cancel a queued build; cancel a running build; delete a finished build with its artifacts and history (permanent); comment on a build; tag a build; pin or unpin a build; assign an investigation of a configuration's problems to a person; mute a test in a project; unmute a test; enable or disable a build agent; pause or resume the whole build queue. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
Who can use a TeamCity connection?+
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my TeamCity data?+
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
How do I connect TeamCity?+
Server URL and Access token. In TeamCity, open your Profile, then Access Tokens, and create a token. A dedicated user with only the roles Memtro needs is safer.
Connect TeamCity in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.