[Azure Functions] Improve local NuGet build script, follow-up by lucaspimentel · Pull Request #8188 · DataDog/dd-trace-dotnet

lucaspimentel · 2026-02-10T18:45:46Z

Summary of changes

Use separate Nuke verbosity levels for download (quiet) vs build (normal) targets
Skip building net461 in local dev script (commented out)
add this build script to CODEOWNERS
Suppress CheckEolTargetFramework warning about net6.0 EOL

Reason for change

After #8174 changed default verbosity to quiet, the package path output was suppressed, making it harder to locate the generated .nupkg file during local development.

Implementation details

In tracer/tools/Build-AzureFunctionsNuget.ps1, split $nukeVerbosity into two variables:

$nukeVerbosityDownload: verbose/quiet for DownloadBundleNugetFromBuild
$nukeVerbosityBuild: verbose/normal for BuildAzureFunctionsNuget (shows package path)

Bonus: In tracer/src/Datadog.AzureFunctions/Datadog.AzureFunctions.csproj, removeCheckEolTargetFramework so we inherit false from a parent directory and suppress the net6.0 EOL warning.

Test coverage

Manually tested.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a9fb6e9d9d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

tracer/build/_build/Build.cs

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>

andrewlock · 2026-02-13T13:10:20Z

.github/CODEOWNERS

 /tracer/test/Datadog.Trace.ClrProfiler.Managed.Tests/HttpBypassTests.cs         @DataDog/tracing-dotnet @DataDog/apm-serverless @DataDog/serverless-azure-and-gcp
 /tracer/samples/AzureFunctionsWithAgentLessLogging/                             @DataDog/tracing-dotnet @DataDog/apm-serverless @DataDog/serverless-azure-and-gcp
 /docs/development/**/AzureFunctions*.md                                         @DataDog/tracing-dotnet @DataDog/apm-serverless @DataDog/serverless-azure-and-gcp
+/tracer/tools/Build-AzureFunctionsNuget.ps1                                     @DataDog/apm-serverless


We normally give dual ownership to these, to make it easier to merge when team sizes are small

Suggested change

/tracer/tools/Build-AzureFunctionsNuget.ps1 @DataDog/apm-serverless

/tracer/tools/Build-AzureFunctionsNuget.ps1 @DataDog/tracing-dotnet @DataDog/apm-serverless @DataDog/serverless-azure-and-gcp

Good point. I can update this in #8173.

andrewlock · 2026-02-13T13:11:02Z

tracer/tools/Build-AzureFunctionsNuget.ps1

+$nukeVerbosityDownload = if ($verbose) { 'verbose' } else { 'quiet' }
+$nukeVerbosityBuild = if ($verbose) { 'verbose' } else { 'normal' }


do you really want verbose? Or do you want to keep the same 'normal' as verbose? Because verbose is verbose

Only for troubleshooting. Trying to be a good PowerShell citizen following conventions, etc 😅 If you pass -Verbose to the ps1 script, it should be verbose.

andrewlock · 2026-02-13T13:11:38Z

tracer/tools/Build-AzureFunctionsNuget.ps1

+# Write-Verbose "Publishing Datadog.Trace (net461) to bundle folder."
+# dotnet publish "$tracerDir/src/Datadog.Trace" -c Release -o "$tracerDir/src/Datadog.Trace.Bundle/home/net461" -f 'net461' -v $dotnetVerbosity


Is this meant to be commented out?

Suggested change

# Write-Verbose "Publishing Datadog.Trace (net461) to bundle folder."

# dotnet publish "$tracerDir/src/Datadog.Trace" -c Release -o "$tracerDir/src/Datadog.Trace.Bundle/home/net461" -f 'net461' -v $dotnetVerbosity

Write-Verbose "Publishing Datadog.Trace (net461) to bundle folder."

dotnet publish "$tracerDir/src/Datadog.Trace" -c Release -o "$tracerDir/src/Datadog.Trace.Bundle/home/net461" -f 'net461' -v $dotnetVerbosity

Funny story. We include net461 in the Azure Functions nuget package, but all C# Azure Functions code is behind #if !NETFRAMEWORK, so we don't really support .NET Framework. (I didn't realize this until after the nuget was first released.)

So, for purposes of dev testing (which is what this script is for), building net461 is a waste of time.

lucaspimentel requested a review from a team as a code owner February 10, 2026 18:45

github-actions bot added the area:builds project files, build scripts, pipelines, versioning, releases, packages label Feb 10, 2026

lucaspimentel changed the title ~~Output Azure Functions NuGet package path~~ [Azure Functions] Output Azure Functions NuGet package path in local dev script build Feb 10, 2026

chatgpt-codex-connector bot reviewed Feb 10, 2026

View reviewed changes

tracer/build/_build/Build.cs Outdated Show resolved Hide resolved

lucaspimentel force-pushed the lpimentel/improve-azure-functions-nuget-build-script-2 branch from a9fb6e9 to 99238f6 Compare February 10, 2026 19:18

lucaspimentel requested a review from a team as a code owner February 10, 2026 19:18

github-actions bot added the area:serverless label Feb 10, 2026

lucaspimentel changed the title ~~[Azure Functions] Output Azure Functions NuGet package path in local dev script build~~ Use normal verbosity for Azure Functions build Feb 10, 2026

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 Feb 10, 2026

lucaspimentel force-pushed the lpimentel/improve-azure-functions-nuget-build-script-2 branch from 99238f6 to 14525a7 Compare February 10, 2026 19:48

lucaspimentel requested a review from a team as a code owner February 10, 2026 19:48

lucaspimentel requested a review from kathiehuang February 10, 2026 19:48

lucaspimentel force-pushed the lpimentel/improve-azure-functions-nuget-build-script-2 branch from 14525a7 to e8e87a3 Compare February 10, 2026 19:54

lucaspimentel changed the title ~~[Azure Functions] Restore normal verbosity for in local build script, log the nupkg path~~ Improve Azure Functions local build script Feb 10, 2026

lucaspimentel removed the request for review from kathiehuang February 10, 2026 19:55

lucaspimentel changed the title ~~Improve Azure Functions local build script~~ [Azure Functions] Improve local NuGet build script, follow-up Feb 10, 2026

lucaspimentel enabled auto-merge (squash) February 10, 2026 20:01

lucaspimentel requested a review from jcstorms1 February 10, 2026 20:05

jcstorms1 approved these changes Feb 10, 2026

View reviewed changes

This comment was marked as off-topic.

Sign in to view

lucaspimentel force-pushed the lpimentel/improve-azure-functions-nuget-build-script-2 branch 3 times, most recently from d62c1ce to 6b7d007 Compare February 12, 2026 00:21

This comment was marked as off-topic.

Sign in to view

lucaspimentel added 4 commits February 12, 2026 14:12

disable CheckEolTargetFramework

c6e785f

skip building for net461

c08e0cf

Use separate verbosity for download and build

2477a01

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>

add script to CODEOWNERS

c6383a4

add script to excluded files in pr trigger

ceb6cb6

lucaspimentel force-pushed the lpimentel/improve-azure-functions-nuget-build-script-2 branch from 6b7d007 to ceb6cb6 Compare February 12, 2026 20:46

This comment was marked as off-topic.

Sign in to view

andrewlock approved these changes Feb 13, 2026

View reviewed changes

lucaspimentel merged commit 9d1dcc7 into master Feb 13, 2026
142 checks passed

lucaspimentel deleted the lpimentel/improve-azure-functions-nuget-build-script-2 branch February 13, 2026 13:11

github-actions bot added this to the vNext-v3 milestone Feb 13, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Azure Functions] Improve local NuGet build script, follow-up#8188

[Azure Functions] Improve local NuGet build script, follow-up#8188
lucaspimentel merged 5 commits intomasterfrom
lpimentel/improve-azure-functions-nuget-build-script-2

lucaspimentel commented Feb 10, 2026 •

edited

Loading

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

andrewlock Feb 13, 2026

Uh oh!

lucaspimentel Feb 13, 2026

Uh oh!

andrewlock Feb 13, 2026

Uh oh!

lucaspimentel Feb 13, 2026 •

edited

Loading

Uh oh!

andrewlock Feb 13, 2026

Uh oh!

lucaspimentel Feb 13, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	/tracer/tools/Build-AzureFunctionsNuget.ps1 @DataDog/apm-serverless
	/tracer/tools/Build-AzureFunctionsNuget.ps1 @DataDog/tracing-dotnet @DataDog/apm-serverless @DataDog/serverless-azure-and-gcp

		$nukeVerbosityDownload = if ($verbose) { 'verbose' } else { 'quiet' }
		$nukeVerbosityBuild = if ($verbose) { 'verbose' } else { 'normal' }

		# Write-Verbose "Publishing Datadog.Trace (net461) to bundle folder."
		# dotnet publish "$tracerDir/src/Datadog.Trace" -c Release -o "$tracerDir/src/Datadog.Trace.Bundle/home/net461" -f 'net461' -v $dotnetVerbosity

Conversation

lucaspimentel commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary of changes

Reason for change

Implementation details

Test coverage

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

andrewlock Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

lucaspimentel Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

andrewlock Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

lucaspimentel Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

andrewlock Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

lucaspimentel Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

lucaspimentel commented Feb 10, 2026 •

edited

Loading

lucaspimentel Feb 13, 2026 •

edited

Loading