dotnet pack/fix-nuspecs is still slow
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
We need to ensure that all commands we execute from within msbuild are either one-time or blasing fast. Otherwise the experience with multiple projects is really really bad.
This issue tracks the "dotnet pack" scenario ("dotnet restore/build" was https://github.com/fsprojects/Paket/pull/2675).
- A quick gain is getting rid of
Argu
I don't know other options yet, we might need to profile fix-nuspecs.
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.
Research direction
Start by profiling the fix-nuspecs path used by dotnet pack, with attention to commands executed from within MSBuild and the stated Argu cost. Compare the pack scenario with the restore/build work referenced in pull request 2675; done means the identified one-time or slow operations no longer make multi-project packing unnecessarily slow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100