Use Poetry with JFrog CLI

Run Poetry commands with Artifactory integration and optional build-info collection.

This topic covers the following tasks:

• Configure Poetry for Artifactory (jf poetry-config)
• Run Poetry commands (jf poetry)

When to Use

Use jf poetry if your Python project uses Poetry (with pyproject.toml) for dependency management. For pip-based projects, use jf pip. For Pipenv-based projects, use jf pipenv. For uv-managed projects, use jf uv.

Prerequisites

• Poetry must be installed and available on your $PATH.
  • Recommended: pipx install poetry (automatically adds Poetry to your PATH).
  • pip: pip install poetry. On macOS, pip installs Poetry to ~/Library/Python/X.Y/bin/, which is not on $PATH by default. After installing, run:
    Bash

    export PATH="$PATH:$(python3 -m site --user-base)/bin"

    Add this line to your shell profile (~/.zshrc or ~/.bashrc) to make it permanent.
• Run jf poetry-config in the project directory before the first install (Wrapped Mode only).
• Configure a server with jf config add or jf c add.
• Authentication to Artifactory is required.
• For Native Mode, configure Poetry via Artifactory's Set Me Up instructions instead.

Configuration: jf poetry-config

Generate Poetry build configuration for dependency resolution. Run this once per project before your first install.

To configure Poetry for Artifactory:

1. From your project directory, run jf poetry-config with your Artifactory server ID and PyPI resolution repository (see Non-Interactive Configuration with Flags).
2. Confirm the generated config under .jfrog/projects/poetry.yaml (see How to Verify).

Synopsis

jf poetry-config [options]

Aliases: poc

Configuration Options

Configuration Examples

View Help

jf poetry-config --help

Non-Interactive Configuration with Flags

jf poetry-config --server-id-resolve=<server-id> --repo-resolve=<repo-name>

Where:

• <server-id>: The server ID configured using jf config add
• <repo-name>: The name of the PyPI repository in Artifactory

For example:

jf poetry-config --server-id-resolve=my-server --repo-resolve=pypi-virtual

Why Run Config First?

You must run jf poetry-config before jf poetry install (Wrapped Mode only). The config creates .jfrog/projects/poetry.yaml for dependency resolution through Artifactory. Without it, jf poetry does not know where to fetch packages.

Configuration Notes

• Config sets resolution only: jf poetry-config configures dependency resolution but not a deployer repository. To publish, pass --repository directly on jf poetry publish (Wrapped Mode) or use native poetry publish (Native Mode).
• Run once per project: Re-run when changing the resolution repository.

Expected Output

$ jf poetry-config --server-id-resolve=my-server --repo-resolve=pypi-virtual
[Info] poetry build config successfully created.

How to Verify

After running, confirm the configuration exists:

cat .jfrog/projects/poetry.yaml

Expected file contents:

version: 1
type: poetry
resolver:
    repo: pypi-virtual
    serverId: my-server

Build: jf poetry

Run Poetry commands with Artifactory integration and optional build-info collection.

To run Poetry with Artifactory integration:

1. Ensure jf poetry-config has been run in the project directory when using Wrapped Mode (see Configuration).
2. Run jf poetry with the Poetry subcommand and arguments you need, adding --build-name and --build-number when you want build-info (see Build Examples).

Synopsis

jf poetry <poetry-arguments> [options]

Aliases: none

Arguments

Build Options

Build Examples

Help

jf poetry --help

Install with Build-Info

jf poetry install --build-name=my-app --build-number=1

Expected output (Wrapped Mode):

[Info] Running Poetry install.
[Info] Added tool.poetry.source name:"<repo-name>" url:"https://<server>/artifactory/api/pypi/<repo-name>"
[Info] Running Poetry update
Updating dependencies
Resolving dependencies...
Writing lock file

Add Dependencies

jf poetry add <package-name>

Poetry Execution Modes

JFrog CLI supports two execution modes for Poetry.

Wrapped Mode (Default)

• Uses jf poetry-config settings
• Injects tool.poetry.source entries into pyproject.toml
• May call poetry update during dependency resolution
• May modify poetry.lock
• Automatically collects build-info when provided --build-name / --build-number

Native Mode

Enable using:

export JFROG_RUN_NATIVE=true

In Native Mode, JFrog CLI:

• Delegates to the native Poetry client without injecting configuration
• Does not inject tool.poetry.source into pyproject.toml
• Does not call poetry update
• Does not modify poetry.lock
• Does not apply jf poetry-config values or JFrog CLI YAML (.jfrog/projects/*.yaml) configuration
• Relies entirely on Poetry's own configuration (as set via Artifactory Set Me Up)
• Still collects build-info when --build-name and --build-number are provided via jf poetry
• Ensures deterministic, reproducible builds

Install: Wrapped vs Native

Wrapped Mode Install

jf poetry install --build-name=my-python-app --build-number=1.2.0

Wrapped Mode behavior:

• May implicitly run poetry update
• May modify poetry.lock
• May inject repository sources into pyproject.toml

Use Native Mode if you require full lockfile fidelity.

Native Mode Install

export JFROG_RUN_NATIVE=true

# With build-info collection
jf poetry install --build-name=my-python-app --build-number=1.2.0

# Or directly (no build-info)
poetry install

Publish: Wrapped vs Native

Wrapped Mode Publish

jf poetry publish --repository pypi-local --no-interaction --build-name=my-python-app --build-number=1.2.0

Behavior:

• May inject tool.poetry.source into pyproject.toml
• May update dependency metadata

Use Native Mode to prevent any modifications.

Native Mode Publish

export JFROG_RUN_NATIVE=true

# With build-info collection
jf poetry publish --no-interaction --build-name=my-python-app --build-number=1.2.0

# Or directly (no build-info)
poetry build
poetry publish --no-interaction -r <REPO_ALIAS>

Credentials must be configured via Set Me Up.

Environment Variable

For a cross-tool comparison of Native Mode across Maven, Gradle, npm, and Poetry, see the dedicated Native Mode page.

Universal Package Note

JFrog CLI is a pass-through to Poetry for execution and output. Output format and behavior belong to Poetry. If Poetry changes its output in a newer version, JFrog CLI honors that without any custom adjustment.

Important Notes

• Config required first: Run jf poetry-config in the project directory before your first install (Wrapped Mode only).
• Resolution only: Poetry config currently supports dependency resolution. For publishing, use jf poetry publish (Wrapped Mode) or Poetry's native poetry publish (Native Mode).
• Poetry commands: All standard Poetry arguments work (install, add, update, lock, and others).
• Build-info: Use --build-name and --build-number, then publish with jf rt build-publish.

CI/CD Example: GitHub Actions

# .github/workflows/build.yml
steps:
  - uses: actions/checkout@v4
  - name: Setup JFrog CLI
    uses: jfrog/setup-jfrog-cli@v4
    env:
      JF_URL: ${{ vars.JF_URL }}
      JF_ACCESS_TOKEN: ${{ secrets.JF_ACCESS_TOKEN }}
  - name: Setup Python
    uses: actions/setup-python@v5
    with:
      python-version: '3.12'
  - name: Install Poetry
    run: |
      pip install poetry
      echo "$(python3 -m site --user-base)/bin" >> $GITHUB_PATH
  - name: Configure Poetry
    run: jf poetry-config --server-id-resolve=setup-jfrog-cli-server --repo-resolve=pypi-virtual
  - name: Install dependencies
    run: jf poetry install --build-name=my-python-app --build-number=${{ github.run_number }}
  - name: Publish package
    run: jf poetry publish --repository pypi-local --no-interaction --build-name=my-python-app --build-number=${{ github.run_number }}
  - name: Publish build info
    run: jf rt build-publish my-python-app ${{ github.run_number }}

Troubleshooting

Enable debug logging: export JFROG_CLI_LOG_LEVEL=DEBUG

Frequently Asked Questions

This section provides answers to frequently asked questions about using Poetry with JFrog CLI.

Related Topics

• Build Tools Overview
• Native Mode
• Use JFrog CLI Package Alias
• Supported Package Manager Versions