[Partner Release Pipelines] Fail if there are no files to copy or sign
Open
Central-EngSys
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
Our partner release pipelines currently "succeed" even if there were no files to copy or sign. Example:
https://dev.azure.com/azure-sdk/internal/_releaseProgress?_a=release-environment-logs&releaseId=22737&environmentId=28363
Can the pipeline be changed to fail fast, as soon as it detects no files?
Contributor guide
Research direction
Review the partner release pipeline definition and the linked Azure DevOps release log (releaseId 22737, environmentId 28363) first. Trace where the copy and signing inputs are detected, then verify that an empty file set causes an immediate failure rather than a successful release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100