> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/integrations/snyk-ci-cd-integrations/teamcity-jetbrains-integration-using-the-snyk-security-plugin/teamcity-integration-use-snyk-in-your-build.md).

# TeamCity integration: use Snyk in your build

For any Project, you can add Snyk to your build to scan the code while you build and to fail the build for vulnerabilities, based on your configurations.

Snyk recommends running a build with the Snyk Security step before deployment, to ensure an excellent security posture.

For additional information about TeamCity and its features, refer to the [TeamCity documentation](https://www.jetbrains.com/help/teamcity/teamcity-documentation.html).

The following explains **how to configure your build with a Snyk step**.

* Add the Snyk step to a new or existing Project:
  * For new Projects, after configuring the Git repo from which to create the build, activate the auto-detect feature to automatically identify relevant steps for your Project build.
  * For existing Projects, navigate to **edit the project build steps**.\
    \
    When the Snyk step has been added, **Snyk Security** appears in the list of suggested steps, and the current test policy appears in the **Parameters Description** column:

![Snyk Security in the list of suggested build steps](/files/6Se9HBTqB85E8VUwrqV6)

* Navigate to configure the Snyk Security step as follows:
  * Click anywhere on the **Snyk Security** row to open the configuration screen, or
  * For existing Projects, click **Add build step** to open the configuration screen.

![Configure Snyk security for TeamCity](/files/JH2ChyfZoXiKCxtulEJI)

* Configure the TeamCity fields (**Runner type**, **Step name**, and **Execute Step** (an advanced option)).
* Optionally, click **Show advanced options** to display additional fields and Snyk parameters:

![Additional Snyk parameters](/files/Bk2EweV4lQV2DlLUglOX)

* Configure **Snyk Settings** and **Snyk Tool Settings**. For more information, see [TeamCity configuration parameters](/developer-tools/integrations/snyk-ci-cd-integrations/teamcity-jetbrains-integration-using-the-snyk-security-plugin/teamcity-configuration-parameters.md).
* When the configuration is complete, run the build. When the Snyk Security step ends successfully, you can navigate to the **Snyk Security Report** tab to view results within TeamCity and to navigate to the Snyk UI for further action:

![Snyk test report](/files/oJwe1WOKOUsCemwNiHvQ)

* From the top of the report, click **View on Snyk.io** to view the snapshot and vulnerability information directly from the Snyk Web UI.


---

# 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.snyk.io/developer-tools/integrations/snyk-ci-cd-integrations/teamcity-jetbrains-integration-using-the-snyk-security-plugin/teamcity-integration-use-snyk-in-your-build.md?ask=<question>&goal=<endgoal>
```

`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.