You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
Run-AlValidation should support baselinePackageCachePath paramter.
We had an Issue around Breaking Changes where the solution was to configure the baselinePackageCachePath in AppSourceCop.json.
Run-AlValidation still fails so i think a parameter like baselinePackageCachePathArtifactUrl (or something like that) is required.
Scripts used to create container and cause the issue
I can definitely repro this.
I will talk to Quentin to figure out why this should be needed
All packages are downloaded to the packageCachePath - which I think should work.
the underlying problem no longer exists. thus, this problem can also no longer be reproduced.
I think we can close the ticket and just hope that msft does not move objects from one app to another again. :)
Describe the issue
Run-AlValidation should support
baselinePackageCachePath
paramter.We had an Issue around Breaking Changes where the solution was to configure the baselinePackageCachePath in AppSourceCop.json.
Run-AlValidation still fails so i think a parameter like baselinePackageCachePathArtifactUrl (or something like that) is required.
Scripts used to create container and cause the issue
Demo Solution with Compiled Apps: BusinessChartBugDemo.zip
Full output of scripts
Additional context
The text was updated successfully, but these errors were encountered: