microsoft / microsoft/react-native-windows
Don't attempt to publish build artifacts in PR if they do not exist
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
The GitHub view of AZP failures shows the most recent failure. This almost always shows the incorrect root cause error below:
This is because we unconditionally try to upload build artifacts, even if an earlier step to produce them fails. We should avoid attempting to publish these artifacts in the case where they might not exist.
Contributor guide
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.
Research direction
Start by locating the Azure Pipelines configuration and the step that publishes build artifacts. Check how an earlier failed artifact-producing step affects the publish step; done means artifact publishing is skipped when the artifacts are absent, while successful builds still publish them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100