> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/teamcity.md). # TeamCity integration Learn how to integrate TeamCity with ilert to automatically send build and deployment alerts, enabling real-time incident notifications and faster response times. [TeamCity](https://www.jetbrains.com/teamcity/) is a powerful continuous integration and delivery (CI/CD) server developed by JetBrains, used to build, test, and deploy code automatically. The ilert integration for TeamCity enables you to automatically send build and deployment alerts to ilert ## In ilert: Create a TeamCity alert source 1. Go to **Alerting** → **Alert sources** and click **Create new alert source**. 2. Search for **TeamCity**, click its tile, and click **Next**. 3. Give your alert source a name, optionally assign teams, and click **Next**. 4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.
The escalation step of the ilert alert source wizard, headed Who should be notified about alerts, with an escalation policy selected and a preview of its escalation rules below.

Pick an existing escalation policy, or generate a basic one without leaving the wizard.

5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving. 6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later. 7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.
## In TeamCity: Enable and configure Webhook 1. On the side bar, navigate to **Admin** -> **Projects** -> **\**.
2. Now click on **Parameters** -> **Add new parameter**.
3. Add following parameter:\ **Name**: `teamcity.internal.webhooks.enable`\ **Value**: `true`
4. Add another parameter:\ **Name**: `teamcity.internal.webhooks.url`\ **Value**: enter the in ilert previous generated alert source url
5. Add another parameter:\ **Name**: `teamcity.internal.webhooks.events`\ **Value**: `BUILD_STARTED; BUILD_FINISHED; BUILD_INTERRUPTED` 6. Click on **Save** to finish the setup.
## FAQ **Will alerts in ilert be resolved automatically?** No, unfortunately TeamCity is not compatible with ilert's resolve event. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ilert.com/integrations/inbound-integrations/teamcity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.