[Azure Functions] Improve local NuGet build script, follow-up by lucaspimentel · Pull Request #8188 · DataDog/dd-trace-dotnet
lucaspimentel
changed the title
Output Azure Functions NuGet package path
[Azure Functions] Output Azure Functions NuGet package path in local dev script build
lucaspimentel
changed the title
[Azure Functions] Output Azure Functions NuGet package path in local dev script build
Use normal verbosity for Azure Functions build
lucaspimentel
changed the title
Use normal verbosity for Azure Functions build
[Azure Functions] Restore normal verbosity for in local build script, log the nupkg path
lucaspimentel
changed the title
[Azure Functions] Restore normal verbosity for in local build script, log the nupkg path
Improve Azure Functions local build script
lucaspimentel
changed the title
Improve Azure Functions local build script
[Azure Functions] Improve local NuGet build script, follow-up
Split Nuke verbosity into two variables to control output: - DownloadBundleNugetFromBuild: verbose/quiet - BuildAzureFunctionsNuget: verbose/normal (shows package path) 🤖 Co-Authored-By: Claude Code <noreply@anthropic.com>
lucaspimentel
deleted the
lpimentel/improve-azure-functions-nuget-build-script-2
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters