Open megel opened 4 years ago
My current Work-Around is a PowerShell Tasks with:
$headers = @{ "Authorization" = "Bearer $(System.AccessToken)"; "Content-Type" = "application/json"; }
$uri = "https://pkgs.dev.azure.com/$([string]::Join("/", ([uri]$env:SYSTEM_TEAMFOUNDATIONSERVERURI).Segments[1].TrimEnd('/'), $env:SYSTEM_TEAMPROJECT).Trim('/'))/_apis/packaging/feeds/$(ArtifactFeed)/upack/packages/$(PackageName)/versions/$(PackageVersion)?api-version=5.1-preview.1"
$body = @{ views = @{ op = "add"; path = "/views/-"; value = "$(ReleaseView)" } } | ConvertTo-Json -Compress
Write-Host "Get packages from '$uri' $($headers | ConvertTo-Json -Compress)" -f Gray
(Invoke-WebRequest -Method Patch -Body $body -uri $uri -Headers $headers -UseBasicParsing)
The Org vs. Project scope has been fixed. Is this issue resolved now?
The UI for project vs org has been fixed too now. The precious fix only worked in YAML.
Likely fixed now: https://github.com/renevanosnabrugge/vsts-promotepackage-task/pull/54
The Log:
The Task Configuration: (Variables are OK)
Lookup Package from Feed FAILS:
The Package (Universal) in Asset Store (Project Scope)
Release Pipeline can access the package:
I guess, Microsoft has changed something at the Asset Store. Package Feeds are now Organization vs. Project Scoped.
Version 1.x works, but I can't select this version from a new created project :/