GitHub Actions: Artifactory Upload Creates Duplicate Nested Paths

[stshta]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Misc

Discussion Details

Hi everyone,

I’m currently trying to upload a signed .exe file to Artifactory (https://global-artifacts.com/) using GitHub Actions.
However, I keep running into a nested repository path issue:

Whenever I try to upload to:
Repo name /artifactory/dev-repo /signed-exe

it creates another duplicate nested path inside it (like .../artifactory/dev-repo/signed-exe/artifactory/dev-repo/signed-exe).

Has anyone run into this issue before or know how to fix it?
I’d appreciate any tips on how to correctly configure the upload path so this nesting doesn’t happen.

Thanks in advance for your help!

[ALOITH-exe]

1. Understand Why the Nesting Happens

When you run:

Repo name /artifactory/dev-repo /signed-exe

Artifactory interprets /artifactory/dev-repo as part of the file path, so when the action uploads, it ends up nesting like:

.../artifactory/dev-repo/signed-exe/artifactory/dev-repo/signed-exe

This usually happens because:

You are including the repo path twice — once in the repository or target setting and again in the file path.

Or you’re passing a local directory with the full remote path included, so the action appends it twice.

2. Correct GitHub Actions Example

Here’s the correct way to upload a signed .exe to Artifactory using GitHub Actions and JFrog CLI:

name: Upload signed exe to Artifactory

on:
push:
branches:
- main

jobs:
upload:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4

  - name: Install JFrog CLI
    uses: jfrog/setup-jfrog-cli@v3
    with:
      version: latest

  - name: Configure Artifactory
    run: |
      jfrog config add my-server \
        --artifactory-url=https://global-artifacts.com/artifactory \
        --user ${{ secrets.ARTIFACTORY_USER }} \
        --password ${{ secrets.ARTIFACTORY_PASSWORD }}

  - name: Upload Signed EXE
    run: |
      # Correct target format: <repo-name>/<path-inside-repo>/<file>
      jfrog rt upload "./signed-exe/myfile.exe" "dev-repo/signed-exe/"

3. Key Rules to Avoid Nesting

Never include /artifactory in the target path.

The CLI automatically handles the /artifactory/ part.

Use only: dev-repo/signed-exe/

Use a clean local path for the source file:

Example: ./signed-exe/myfile.exe

Do not include repo names or remote folder structure here.

Ensure globbing is correct:
If uploading multiple files:

jfrog rt upload "signed-exe/*.exe" "dev-repo/signed-exe/"

Verify upload with dry run:

jfrog rt upload --dry-run "signed-exe/*.exe" "dev-repo/signed-exe/"

This will show you exactly where files will land before committing.

4. Example Result

With the above configuration, your Artifactory structure will be:

dev-repo/
signed-exe/
myfile.exe

Instead of:

dev-repo/
signed-exe/
artifactory/
dev-repo/
signed-exe/
myfile.exe

5. If You’re Using an Upload Action Instead of CLI

If you’re using an action like actions/upload-artifact or a custom Artifactory action, check for:

repository or targetPath inputs — don’t include the full path twice.

The target should only be dev-repo/signed-exe/, not artifactory/dev-repo/signed-exe/.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬