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

Artifacts: inspecting directory structure & download specifiers? #14896

Closed
anlsh-msft opened this issue Aug 24, 2020 · 1 comment
Closed

Artifacts: inspecting directory structure & download specifiers? #14896

anlsh-msft opened this issue Aug 24, 2020 · 1 comment
Labels
needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@anlsh-msft
Copy link

anlsh-msft commented Aug 24, 2020

The Problem

Our team is using Azure DevOps to manage our builds, and every so often needs to download artifacts from pipelines. We wanted a CLI for doing so, and some research turned up the Azure CLI.

However, it doesn't look like the CLI has all the functionality which the DevOps website does.

For one, the website can detect whether an uploaded artifact is a folder, and will allow you to navigate the tree structure to download specific parts of the artifact. To illustrate, each folder has an individual download option on the UI

devops-ui

However, from what I can tell neither the Azure CLI nor the REST API supports this functionality. The list and download commands only work with the top-level files/folders themselves, and if an artifact is a folder then there's no way to download sub directories without downloading the entire thing.

Proposed Solution

It would be very nice if we could do something like an az pipelines runs artifact tree --run-id 9999 to get output something like what GNU tree would produce. It would also be very nice to be able to download files via pattern matching, eg

az pipelines runs artifact download --run-id 9999 --outfile outfile artifact1/log.txt

at minimum and ideally things like

az pipelines runs artifact download --run-id 9999 --outfile outfile artifact1/*.txt

Hopefully I'm not missing existing functionality? And if not, would you consider adding this?

@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Aug 24, 2020
@anlsh-msft
Copy link
Author

It looks like this actually belongs in azure-devops-cli-extension, so I'll move it there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

1 participant