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
Fix scoped builds: check BuildTargetingString glob match instead of directory existence
When BuildTargetingString is set, split it by comma and test each artifact
name against the glob patterns using PowerShell -like before attempting to
publish. Non-matching packages are skipped with a clear log message.
Closes#42014
Agent-Logs-Url: https://github.com/Azure/azure-sdk-for-python/sessions/88e37a34-ffce-4971-91c0-223321039c44
Co-authored-by: scbedd <45376673+scbedd@users.noreply.github.com>
# When a build is scoped via BuildTargetingString, only targeted packages have
393
-
# artifact directories. Skip gracefully if this package was not part of the build.
394
-
if (-not (Test-Path $artifactDir)) {
395
-
Write-Host "Artifact directory for ${{artifact.name}} not found at '$artifactDir'. Package was not targeted by the current build scope, skipping publish."
396
-
exit 0
390
+
# If BuildTargetingString is set, check whether this artifact matches any of the
391
+
# (possibly comma-separated) glob patterns before attempting to publish.
392
+
# This handles scoped builds where only a subset of packages are built.
0 commit comments