Jenkins Artifactory Plugin (Legacy)

Migrate first: Use the Jenkins JFrog Plugin for new Pipeline work. Install it alongside the Jenkins Artifactory Plugin and migrate existing jobs incrementally.

The Jenkins Artifactory Plugin still supports existing jobs that publish, resolve, promote, or release artifacts with build-info. This page is a focused migration reference, not a complete copy of the plugin's historical domain-specific language (DSL).

This topic covers the following tasks:

• Decide Which Path to Use
• Inventory an Existing Job
• Migrate Incrementally

Decide Which Path to Use

The path you take depends on whether the job already exists and whether it uses legacy release staging.

To decide which path to use:

• New Pipeline: Use the Jenkins JFrog Plugin and its JFrog CLI-like steps.
• Existing Pipeline or Freestyle job: Keep the Jenkins Artifactory Plugin temporarily while you map its behavior.
• Legacy release staging: Also review Jenkins Artifactory Plugin Release Management.

Inventory an Existing Job

An inventory of the current job configuration gives you a baseline to compare against after you migrate.

To inventory an existing job, record these values:

• Artifactory server or your JFrog Platform endpoint and credential ID.
• Resolver and deployment repositories, including differences between snapshot and release repositories.
• Build name, build number, and project key.
• File Specs, legacy patterns, environment collection, and retention settings.
• Package-specific steps and release or promotion actions.

Migrate Incrementally

Migrate one job at a time so your existing builds keep running while you move work to the Jenkins JFrog Plugin.

To migrate a job to the Jenkins JFrog Plugin:

1. Install and configure the Jenkins JFrog Plugin without removing the Jenkins Artifactory Plugin.
2. Choose one representative Pipeline job.
3. Translate one operation at a time to the documented steps of the Jenkins JFrog Plugin.
4. Publish to a non-production target and compare artifact paths and build-info.
5. Confirm the migrated build under Builds in Artifactory.
6. Repeat for dependent jobs, then remove their legacy DSL and plugin dependency.

For an existing job whose DSL is not covered here, consult the Jenkins Artifactory Plugin source and release history. Do not start a new job by copying that legacy DSL.

Troubleshooting

The following table lists common symptoms after a migration and what to check.

Related Topics

• Jenkins JFrog Plugin
• Build Integration
• About Build Info
• Inspect Builds
• Manage Builds