Legacy Build Integration Plugins
Migrate from a legacy build integration plugin to the maintained JFrog replacement.
Use this section only when you maintain an existing job that depends on an older integration. For new automation, start from the Build Integration hub and choose a maintained continuous integration or build-tool path.
Choose a Migration Path
The following table lists the maintained replacement for each legacy build integration.
| Existing integration | Recommended path for new work | Historical page |
|---|---|---|
| Jenkins Artifactory Plugin | Jenkins JFrog Plugin | Jenkins Artifactory Plugin |
| Jenkins Artifactory release staging | Jenkins JFrog workflows and Manage Builds | Legacy release management |
| Bamboo Artifactory Plugin | Run JFrog CLI in Bamboo Script or Command tasks and plan migration from Bamboo Data Center | Bamboo Artifactory Plugin |
| TeamCity Artifactory Plugin | Run JFrog CLI in TeamCity build steps | TeamCity Artifactory Plugin |
| Visual Studio Team Services (VSTS) plugin | JFrog Azure DevOps Extension | VSTS plugin |
| Gradle Artifactory Plugin version 4 guidance | Artifactory Gradle Plugin | Legacy Gradle guidance |
| Ant and Ivy integration | Prefer maintained Maven or Gradle publications, or JFrog CLI | Working with Ivy |
Migrate Safely
To migrate safely to a maintained integration:
- Inventory the jobs that call the legacy plugin or its domain-specific language (DSL).
- Add the maintained integration alongside the legacy integration where both can run side by side.
- Move one job at a time and compare artifact paths, build names, build numbers, and published build-info.
- Confirm the migrated build under Artifactory > Builds before removing the legacy configuration.
- Keep the historical child page available until every dependent job has moved.
A historical page stays available for reference only. It is not a recommendation to start a new job with that plugin.
Related Topics
Updated about 1 month ago
Did this page help you?