Feasability to support a different version control than git
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp, git
- Domain
- build-system
Research direction
Start by reading the ISourceControlFileHashProvider implementation and the Git command that runs git ls-files -z -cmos --exclude-standard. Investigate whether Plastic SCM's cm command can provide the tracked-file list and hashes, then determine what would be required for MSBuildCache to support Plastic SCM.
Written by the indexing model from the issue text.
Description
Hello, at my work we use Plastic SCM (Unity Version Control) and would like to add a caching tool for msbuild. Trying out the local msbuild cache I notice that it seems to use git to build a dictionary of (file, hash of file) and I was wondering if someone could shed some light on how to go about implementing a ISourceControlFileHashProvider for Plastic instead. The git variant which runs git ls-files -z -cmos --exclude-standard seems to make a list of all the tracked files? That's probably doable with cm (the Plastic SCM command line tool) somehow, although I'm not sure it has a git hash-object.
So, dear reader, if you have any thoughts about how to best go about this, please let me know. I suppose one alternative is to just make a local git repo to make MSBuildCache think we are using git.
- Dominant language
- C#
- Stars
- 64
- Forks
- 24
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 2
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.
More from microsoft/MSBuildCache
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
microsoft/MSBuildCache#154 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/MSBuildCache#164 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/MSBuildCache#167 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/MSBuildCache#159 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/MSBuildCache#155 · 1 comment ·
All issues in microsoft/MSBuildCache
Similar issues
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cake-build/cake#5024 ·
-
Frontend status/draft TechnicalDebt
Difficulty 2/5 1-2 days Newbie friendliness 75/100
Altinn/altinn-auth#4143 ·
-
.NET Flaky Test Testing Tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/sentry-dotnet#5617 · 1 comment ·
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·