Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uploading a zip with directory structure without root directory #1846

Closed
flcdrg opened this issue Feb 24, 2023 · 4 comments
Closed

Uploading a zip with directory structure without root directory #1846

flcdrg opened this issue Feb 24, 2023 · 4 comments
Labels
question Further information is requested

Comments

@flcdrg
Copy link

flcdrg commented Feb 24, 2023

Is there a way to get JFrog to create a zip and upload it, where you point at a specific directory and the zip includes the contents of that directory and and subdirectories, but the zip doesn't include the top-level directory itself.

eg. If I use this:

        {
          "files": [
            {
              "pattern": "mydirectory/*",
              "target": "rep/thing.zip",
              "archive": "zip",
              "flat": "false"
            }
          ]
        }

Then the zip file contains a mydirectory directory, but I want it to start with the files and subdirectories under mydirectory

@flcdrg flcdrg added the question Further information is requested label Feb 24, 2023
@RobiNino
Copy link
Contributor

Hi @flcdrg ,
Currently the only available option is to cd into the directory you would like to upload and provide "./*" as pattern.
Placeholders are unfortunately not supported with the archive option.
Thanks

@flcdrg
Copy link
Author

flcdrg commented Mar 13, 2023

Ah.. as I'm using the Azure DevOps extension task, which doesn't offer the ability to change the current directory, I'm out of luck for now.

@RobiNino
Copy link
Contributor

A possible workaround would be to use the JFrog CLI V2 task which supports setting a working directory.
I assume Azure DevOps also supports temporarily changing the working directory, but I can see why this may be a bit inconvenient.

@RobiNino
Copy link
Contributor

RobiNino commented Feb 5, 2025

Hi @flcdrg ,
Looks like you managed to workaround the limitation with changing the working directory.
I'm closing this issue now, feel free to reopen if necessary.
Thanks

@RobiNino RobiNino closed this as completed Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants