Fix scoped builds crashing on integration publishing

[Copilot]

• Understand the new approach: match artifact name against BuildTargetingString globs
• Replace Test-Path check with BuildTargetingString glob matching in Integration stage
• Validate (parallel_validation passed)

Original prompt

Context

Issue: Scoped builds crash on integration publishing
Repo: Azure/azure-sdk-for-python
Issue: #42014 (assigned to @scbedd)

When a developer queues a build that is scoped via BuildTargetingString and attempts to publish to integration with SetDevVersion=true, the build fails because the pipeline expects an artifact/package that was filtered out by the targeting string and therefore does not exist.

The issue body states the desired behavior:

• This should work.
• Integration publishing should gracefully skip publishing a package when the build targeting string doesn't apply (i.e., the package was not built / artifact not produced).

There is a failing Azure DevOps build log referenced in the issue:

• https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5085991&view=logs&j=b1e79959-24d8-5aa9-2799-72d40c3e051b&t=52817674-d19f-518b-48e6-83892d5791a6

Task

Create a PR in Azure/azure-sdk-for-python that fixes the integration publishing pipeline logic so that scoped builds (using BuildTargetingString) do not fail when packages are filtered out.

Requirements

1. Reproduce/understand the failure by inspecting the pipeline scripts/templates used for integration publishing and how they discover expected artifacts.
2. Identify where the pipeline:
   • enumerates packages to publish, and
   • assumes an artifact exists for each enumerated package.
3. Implement a fix so that when a package is not built due to BuildTargetingString filtering (or otherwise absent artifacts), the integration publishing step:
   • skips that package,
   • logs a clear message indicating it was skipped because the artifact wasn’t produced / not targeted,
   • continues publishing remaining targeted packages.
4. Ensure the fix works for both:
   • SetDevVersion=true (dev version publishing) and
   • normal integration publishing scenarios.
5. Add/update tests where feasible (unit tests for scripts, or pipeline-level validation if present). If tests are not practical, add a lightweight validation script step or robust error handling with clear logs.
6. Update any documentation/comments in the pipeline templates to explain the behavior.

Implementation guidance

• Prefer making the logic resilient by checking artifact existence before attempting publish.
• If a manifest/list of built artifacts exists (e.g., output file from the build stage), use it as the source of truth instead of static package enumeration.
• Keep behavior unchanged for non-scoped builds.

PR Deliverables

• Code changes to pipeline templates/scripts that handle integration publishing.
• Any accompanying tests or validation steps.
• PR description should:
  • reference and close Scoped builds crash on integration publishing #42014,
  • explain the root cause,
  • describe the change and why it is safe,
  • include how it was validated.

Acceptance criteria

• Scoped build + integration publish + SetDevVersion=true no longer fails due to missing expected artifacts.
• Untargeted packages are skipped with a clear log message.
• Targeted packages still publish successfully.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Examine the body and my comment on this issue #42014

I want you to submit a PR that resolves this issue. Effectively integration needs to handle when the package is filtered out at the very least.

Feel free to understand the problem and confer with me before executing on a solution.

Assistant: I’ve queued up the PR creation workflow, but I’m currently waiting on your accept/reject response to the permissions prompt before I can proceed with implementing and submitting the fix.

This pull request was created from Copilot chat.

[Copilot]

Pull request overview

This PR updates the Integration publishing logic in the Python release archetype pipeline to avoid attempting integration publishing for packages that were filtered out by a scoped build (BuildTargetingString), addressing failures where expected artifacts were not produced.

Changes:

• Add a BuildTargetingString check in the Integration publish step to skip publishing non-targeted packages with a clear log message.

Show a summary per file

File	Description
eng/pipelines/templates/stages/archetype-python-release.yml	Adds targeting-string matching to skip integration publish for artifacts excluded by scoped builds.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 2

[scbedd]

/check-enforcer override