JFrog Build Offerings by Package Type
Choose the JFrog Artifactory build-info publishing path for your package type or build tool.
This page maps a package type to a code-backed publishing path in JFrog Artifactory. It's the right starting point when you already know the build tool. If your main decision is the CI platform, the Build Integration hub is a better place to begin. For a comparison of the plugin, JFrog CLI, and CI wrapper approaches, see Choose Plugin, CLI, or CI Wrapper.
What This Documentation Tree Owns
Maven and Gradle have plugins in this documentation tree: the Maven Artifactory Plugin and the Artifactory Gradle Plugin. Other package types use JFrog CLI, which is documented in the JFrog Artifactory documentation. This page doesn't provide a second plugin matrix, and it doesn't claim CI task coverage that this documentation tree doesn't own.
The following table shows where each package type or build tool starts.
| Package or build tool | Path in this documentation | Start here |
|---|---|---|
| Maven | Plugin in this documentation tree, or CLI-centric jf mvn in CI | Maven Artifactory Plugin |
| Gradle | Plugin in this documentation tree, or jf gradle in CLI-centric CI | Artifactory Gradle Plugin |
| npm | JFrog CLI | JFrog CLI build tools |
| Go | JFrog CLI | JFrog CLI build tools |
| Python | JFrog CLI | JFrog CLI build tools |
| NuGet or .NET | JFrog CLI | JFrog CLI build tools |
| Docker or OCI | JFrog CLI | JFrog CLI build tools |
| Yarn | JFrog CLI | JFrog CLI build tools |
| Ivy | Established extractor. New work should use Maven or Gradle. | Working with Ivy and Artifactory (Legacy) |
An integration that can run JFrog CLI may support a package workflow without having a dedicated package task. Support varies by platform and by version, so confirm it before you standardize on a combination of CI platform and package type.
CI Integrations That Run the Path
Each CI platform has its own starting page in this documentation tree.
- GitHub Actions: GitHub Actions.
- Jenkins: Jenkins JFrog Plugin.
- GitLab CI: GitLab Templates for JFrog.
- Azure DevOps: JFrog Azure DevOps Extension.
- Bitbucket Pipelines: JFrog Setup CLI Bitbucket Pipe.
- Bamboo: New work uses JFrog CLI in script or command tasks. The Bamboo JFrog Plugin covers existing supported configurations only.
What the Selected Path Produces
A complete publishing workflow associates package operations with the same build name and number, then publishes the resulting build-info record. The following pages cover what happens after publication.
- Inspect Builds shows the modules, artifacts, and dependencies of a published build.
- Manage Builds covers appending, promoting, and retaining published builds.
Related Topics
Updated about 1 month ago