TeamCity

Automate your testing workflow directly from TeamCity CI/CD pipelines.

Enterprise feature

External provider integrations are available on Enterprise plans. Contact the nunu team if you are interested.

What do we need?

TeamCity Base URL: Your TeamCity server URL (e.g., https://teamcity.example.com )
Project ID: The TeamCity project identifier
Access Token: A Personal Access Token with the required API permissions

Project ID

You can find the Project ID in the project settings or in the URL when viewing the project (e.g., yourproject in https://teamcity.example.com/project/yourproject/ ).

Steps to locate it:

Go to Projects in TeamCity.
Select the project you want to integrate.
Open or toggle the Settings view.
Under General Settings, you’ll see the Project Name and Project ID.
Copy the Project ID and paste it into the corresponding field in the Deployment Configuration Editor.

Access Token

API tokens are user-specific and must be created by a user with at least the Project Viewer role.

Steps to generate a token:

Go to your User Profile (usually bottom-left).
Navigate to the Access Tokens tab.
Click Create access token. Set a name and optionally an expiration date.
Under permissions, limit the scope to the project and select:
- Project
  - View project and all parent projects
- Build
  - View build configuration settings
  - View build runtime parameters and data
Create the token and copy it immediately—it cannot be viewed again.

Store your token securely. If lost, you’ll need to generate a new one.

Example Config:

TeamCity Configuration Example

Check out Deployment Configuration for more details on how to configure your deployment settings on nexus and integrate with your CI/CD pipeline integration.