SDK Diff pipeline should discover artifacts from upstream builds with post-build failures
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- build-system, ci-cd, devops
Research direction
Start at the SDK Diff pipeline's artifact download logic and trace the strict expected-name lookup against upstream build artifacts. Use upstream build 2950508 and SDK Diff build 2950719 as reproduction cases; done means a post-build-renamed artifact is discovered by pattern and downloaded instead of failing.
Written by the indexing model from the issue text.
Description
When a post-build step (1ESPT, signing, etc.) fails in the upstream pipeline, artifacts get published under a failure/alternate name instead of the expected name (e.g. SB_Ubuntu2404_Offline_MsftSdk_x64_Artifacts). The SDK Diff pipeline does a strict name lookup, can't find them, and fails — even though the SDK was successfully built.
The artifact download logic should fall back to enumerating available artifacts on the upstream build and matching by pattern when the expected name isn't found.
Example: SDK Diff build 2950719 failed because upstream build 2950508 had a post-build failure.
- Dominant language
- No language data
- Stars
- 287
- Forks
- 146
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 10
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/source-build
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dotnet/source-build#5656 · 2 comments ·
-
area-infra
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dotnet/source-build#5639 · 1 comment ·
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 45/100
dotnet/source-build#5655 ·
-
area-infra
Difficulty 4/5 3-5 days Newbie friendliness 52/100
dotnet/source-build#5636 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
dotnet/source-build#5631 ·
All issues in dotnet/source-build
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oSoWoSo/vOid_Community_repOsitory#147 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
agentic-workflows cascade-suspected
Difficulty 1/5 Under an hour Newbie friendliness 88/100