Fix Azure Pipeline NuGet package generation#884
Conversation
Co-authored-by: vslee <366757+vslee@users.noreply.github.com>
…Directory Co-authored-by: vslee <366757+vslee@users.noreply.github.com>
Fixed in commit 7f3ba2c. The error was caused by invalid parameter names in the DotNetCoreCLI@2 pack task. Changed |
|
@copilot check the pipeline status again |
Co-authored-by: vslee <366757+vslee@users.noreply.github.com>
Updated in commit a575211. The issue was mixing the |
|
@copilot the error is "The task has failed because you are using Ubuntu 24.04 or later without mono installed. See https://aka.ms/nuget-task-mono for more information." |
… issue Co-authored-by: vslee <366757+vslee@users.noreply.github.com>
Fixed in commit 30970c3. Replaced |
Azure Pipeline Fix Plan
Changes Made
Fixed the Azure Pipeline build process to properly generate and publish NuGet packages:
--outputand--version-suffixarguments that interfere with packpackDirectoryparameter tooutputDirconfigurationparameter to avoid conflicts with--no-buildargumentsparameter:--configuration $(BuildConfiguration) --version-suffix prerelease-$(PipelineDate) --no-buildNuGetToolInstaller@1task (not needed)NuGetCommand@2toDotNetCoreCLI@2withcommand: pushnuGetFeedType: internalparameterRoot Cause
The Azure Pipeline was failing due to:
--outputwithdotnet buildwhich places artifacts in non-standard locationspackDirectorydoesn't exist)configurationparameter with--no-buildflag which can cause conflictsNuGetCommand@2which requires Mono on Linux, but Ubuntu 24.04 doesn't have it by defaultThe correct approach is to:
DotNetCoreCLI@2for all .NET operations (build, pack, push) which doesn't require Mono--configurationexplicitly in the arguments when using--no-buildSecurity Summary
No security vulnerabilities introduced or detected in these configuration changes.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.