microsoft / microsoft/react-native-windows
Consolidate logging locations of the rnw PR/CI pipelines
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Our PR validation and CI validation has enabled a bunch of logging, some msbuild logs, some javascript logs, some machine state information, and now a PR is out that adds ETW logging.
Each logging step declares it's own artifacts and upload locations for logging.
It would be really nice if each pipeline, but it msbuild, integration test etc sets up a logging folder on the machine, We update all tasks to place the log files into that folder, and have a single upload task to make that folder availalbe for diagnostics.
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
Review the PR validation and CI validation pipeline logging steps, including msbuild, integration test, JavaScript, machine-state, and ETW logging, to identify each artifact declaration and upload location. Done means each pipeline uses a shared machine logging folder, all tasks place logs there, and one upload task exposes that folder for diagnostics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, devops, observability
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100