Fix scoped builds crashing on integration publishing (#46233)

* 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: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: scbedd <45376673+scbedd@users.noreply.github.com>

Author: 2 people

eng/pipelines/templates/stages/archetype-python-release.yml

@@ -387,6 +387,19 @@ stages:
           - ${{if ne(artifact.skipPublishDevFeed, 'true')}}:
 
             - pwsh: |
+                # If BuildTargetingString is set, check whether this artifact matches any of the
+                # (possibly comma-separated) glob patterns before attempting to publish.
+                # This handles scoped builds where only a subset of packages are built.
+                $targetingString = $env:BUILDTARGETINGSTRING
+                if ($targetingString) {
+                  $globs = $targetingString -split ","
+                  $isTargeted = $globs | Where-Object { "${{artifact.name}}" -like $_.Trim() }
+                  if (-not $isTargeted) {
+                    Write-Host "Package '${{artifact.name}}' does not match BuildTargetingString '$targetingString'. Skipping integration publish."
+                    exit 0
+                  }
+                }
+
                 $fileCount = (Get-ChildItem $(Pipeline.Workspace)/${{parameters.ArtifactName}}/${{artifact.name}} | ? {$_.Name -match "-[0-9]*.[0-9]*.[0-9]*a[0-9]*" } | Measure-Object).Count
 
                 if ($fileCount -eq 0) {