TeamCity Artifactory Plugin (Legacy)
Maintain the legacy TeamCity Artifactory Plugin and migrate new builds to JFrog CLI.
Migrate first: Use JFrog CLI in TeamCity build steps for new automation. This is the only TeamCity integration page in this documentation tree. It does not describe or imply a separate current TeamCity JFrog plugin.
The TeamCity Artifactory Plugin repository remains available for existing jobs. Its code supports publishing, resolving, promoting, and releasing traceable artifacts. The 3.0.x code line targets TeamCity 2025.11. This page covers the following tasks:
Existing Plugin Prerequisites
For plugin 3.0.x, align the TeamCity version and Java runtime with the release requirements before upgrading. Verify the exact release notes and Marketplace package for the version you install.
Preserve Existing Plugin Configuration
Keep your current plugin setup intact so existing jobs continue to publish build-info after you upgrade.
To preserve your existing plugin configuration:
- Record the global Artifactory server configuration and the credentials used by each project.
- Record runner repository selections, build name, build number, and whether release management is enabled.
- Upgrade the plugin in a staging TeamCity instance.
- Run one representative build and confirm artifact paths and build-info links.
- If you use release management, confirm that exactly one supported runner is configured for it.
The plugin also contains generic integration, build triggers, retention, and release-management features. Use the TeamCity Artifactory Plugin source as the exhaustive historical reference.
Migrate a New or Existing Step to JFrog CLI
Move new and existing TeamCity steps to JFrog CLI so your builds follow the current recommended path.
To migrate a new or existing step to JFrog CLI:
- Run documented JFrog CLI commands in a TeamCity command-line step.
- Keep credentials in TeamCity parameters and set stable build name and number values.
- Compare the resulting build-info with the plugin-generated build before removing the old runner integration.
Troubleshooting
The following table lists common symptoms, their likely causes, and the action to take.
| Symptom | Likely cause | Action |
|---|---|---|
| Plugin does not load after upgrade | TeamCity or Java does not meet the selected release requirement | Match the plugin release requirements before installation. |
| Release management reports no runner | No supported runner has release management enabled | Configure one supported runner. The code rejects zero or multiple configured steps. |
| Build link is missing | Build-info was not published or identity changed | Verify publication and compare build name and number. |
Related Topics
Updated 21 days ago