microsoft / microsoft/MSBuildCache
Cache plug-in should provide a way to fix/mitigate full paths in build output files
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 64
- Forks
- 24
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 2
Description
Projects may have full path embedded in the build output, and when those files are copied to a different environment, it often does not work. Today, the only option is to disable the cache for projects being affected by this.
We suggest the plug-in to have a way to patch some of those files in well-known files to partially mitigate this issue.
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
No files or tests are named. Start by mapping how the cache plug-in stores and restores build output files, then identify which well-known files can contain full paths and how they could be patched after retrieval. Done means defining a clear mitigation scope and validating it for projects moved to another environment without disabling the cache.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100