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

NuGet packages created with AzDo pipelines (not GH ones) don't see the locations data files #245

Open
gfmatthews opened this issue Jan 24, 2023 · 2 comments
Assignees
Labels
bug Something isn't working Triage Approved

Comments

@gfmatthews
Copy link
Member

gfmatthews commented Jan 24, 2023

  1. Build the NuGet package using AzDo pipelines with built-in tools (i.e. AzDo's built-in dotnet pack and dotnet build)

Pull the built NuGet package into a new Visual Studio project.

EXPECTED:
Package runs and no dependency issues are found

ACTUAL:
Package fails when trying to find Azure Regions file

@juzuluag
Copy link

Seems like the issue is that using AzDo task NuGetCommand@2 doesn't create the package as expected, which is what is used by the customer. Using DotNetCoreCLI@2 task works as expected and the package contains the files in the format expected. The suggestion here is to use that DotNetCoreCLI instead. A working sample pipeline yml file was send to the user.

@juzuluag
Copy link

juzuluag commented Jan 26, 2023

PR: Green-Software-Foundation#279

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Triage Approved
Projects
None yet
Development

No branches or pull requests

3 participants