search

renevanosnabrugge / vsts-promotepackage-task

Promote a package in VSTS to a Release View
MIT License
21 stars 25 forks source link

Package not found exception #26

Closed andyofengland closed 4 years ago

andyofengland commented 5 years ago

When no changes have been made to the release pipeline or underlying structure; sometimes I get a build failure due to the package not being found:

2019-07-22T11:12:33.5081582Z ##[debug]Caught exception from task script.
2019-07-22T11:12:33.5119333Z ##[debug]Error record:
2019-07-22T11:12:33.6190833Z ##[debug]Package  could not be found
2019-07-22T11:12:33.6206180Z ##[debug]At C:\agent\_work\_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\1.4.3\vsts-promotepackage-task.ps1:151 char:9
2019-07-22T11:12:33.6222998Z ##[debug]+         throw "Package $packageId could not be found"
2019-07-22T11:12:33.6237830Z ##[debug]+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2019-07-22T11:12:33.6252737Z ##[debug]    + CategoryInfo          : OperationStopped: (Package  could not be found:String) [], RuntimeException
2019-07-22T11:12:33.6266410Z ##[debug]    + FullyQualifiedErrorId : Package  could not be found
2019-07-22T11:12:33.6282642Z ##[debug] 
2019-07-22T11:12:33.6306067Z ##[debug]Script stack trace:
2019-07-22T11:12:33.6350458Z ##[debug]at Get-PackageInfo, C:\agent\_work\_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\1.4.3\vsts-promotepackage-task.ps1: line 151
2019-07-22T11:12:33.6363800Z ##[debug]at Set-PackageQuality, C:\agent\_work\_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\1.4.3\vsts-promotepackage-task.ps1: line 164
2019-07-22T11:12:33.6380252Z ##[debug]at Run, C:\agent\_work\_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\1.4.3\vsts-promotepackage-task.ps1: line 221
2019-07-22T11:12:33.6395092Z ##[debug]at <ScriptBlock>, C:\agent\_work\_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\1.4.3\vsts-promotepackage-task.ps1: line 230
2019-07-22T11:12:33.6409542Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-07-22T11:12:33.7112525Z ##[debug]at <ScriptBlock>, <No file>: line 22
2019-07-22T11:12:33.7113293Z ##[debug]at <ScriptBlock>, <No file>: line 18
2019-07-22T11:12:33.7135972Z ##[debug]at <ScriptBlock>, <No file>: line 1
2019-07-22T11:12:33.7184820Z ##[debug]Exception:
2019-07-22T11:12:33.7270906Z ##[debug]System.Management.Automation.RuntimeException: Package  could not be found
2019-07-22T11:12:33.7486462Z ##[error]Package  could not be found
2019-07-22T11:12:33.7486841Z ##[debug]Processed: ##vso[task.logissue type=error]Package  could not be found
2019-07-22T11:12:33.7494599Z ##[debug]Processed: ##vso[task.complete result=Failed]

If I look at the build definition, I see a warning icon on each of the promote tasks and I have to then re-point it to the package thats defined within the Azure Artifact store.

The error only happens on this plugin and it is across all releases within the project - I have not yet enabled th eplugin on builds in different projects yet, so am unable to test this.

The last time the task worked was last week and yet today it failed so I am assuming (perhaps wrongly) that when the underlying plugin code is updated, it loses the link to the artefact store.

NightOwl888 commented 5 years ago

See my comment here. This looks to be the same issue.