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

DownloadPackage doesn't support latest version #12333

Closed
evertonmc opened this issue Feb 11, 2020 · 1 comment · Fixed by #12334
Closed

DownloadPackage doesn't support latest version #12333

evertonmc opened this issue Feb 11, 2020 · 1 comment · Fixed by #12334

Comments

@evertonmc
Copy link
Contributor

Note

Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo

For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks

If you have an issue or request for the Azure Pipelines service, use developer community instead:

https://developercommunity.visualstudio.com/spaces/21/index.html )

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Feature

Enter Task Name: DownloadPackage

  • Server - Azure Pipelines or TFS on-premises?
    Azure DevOps Server 2019.1.1

Issue Description

DownloadPackage doesn't support selecting the latest package at runtime

@lucianiz
Copy link

lucianiz commented Feb 2, 2021

DownloadPackage doesn't support latest version for universal packages.
There is a check

  if (packageType === "upack") {
            return await downloadUniversalPackage(downloadPath, feed.projectId, feed.feedId, packageId, version, filesPattern);
        }

that is done before checking if version = "latest", this causes "latest" version to work for all package types except universal packages, we are using universal packages only, we really need this feature, currently I'm doing workarounds for linux but we now have windows deployments that would require duplicating the workarounds for all windows piplines.

@herenhuang would it be possible to re-open this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants