Working with Gradle (Legacy Guidance)

Migrate first: Use the current Artifactory Gradle Plugin documentation for new work. Keep this page only to identify and retire version 4-era configuration.

The current Artifactory Gradle Plugin adds an artifactoryPublish task that publishes configured artifacts and build-info. Version 6 requires Gradle 8 or later and is primarily intended and tested for Gradle 9 or later.

Identifying an Older Configuration

A build is likely using the older path when it declares build-info-extractor-gradle:4.+, uses the version 4 convention DSL, or depends on configuration names and attributes removed by later plugin versions.

Migrate an Existing Build

To migrate an existing build to the current Artifactory Gradle Plugin:

1. Record the existing publication names, release and snapshot repository keys, build name, and build number.

2. Review the version 5-to-6 migration notes in the Artifactory Gradle Plugin README.

3. Update the plugin version and satisfy the current Gradle and Java prerequisites documented there.

4. Map the existing publication selection to the current publications configuration.

5. Run the publish task against a non-production repository:

   Shell

   ./gradlew artifactoryPublish

6. Compare the artifact paths and build-info with the legacy run before switching CI.

The version 4 DSL isn't a starting point for new projects. The Artifactory Gradle Plugin documentation and the plugin README are the maintained configuration references.

Troubleshooting Gradle Migration

The following table lists the symptoms you might see after a migration, their likely causes, and the action to take.

Related Topics

• Artifactory Gradle Plugin
• Build Integration
• About Build Info
• Inspect Builds
• Manage Builds