Distributed compilation #11
Labels
No Label
FCKPTN
WIP
bug
docs done
docs needed
duplicate
enhancement
feature
gemini
invalid
legal-ish
needs help
onionz
proposal
question
resolved
security
spam
todo
upstream-related
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: dotya.ml/community#11
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Provide handling of DistCC https://github.com/distcc/distcc that would allow crowdsourcing with the intention to support development through providing spare resources with optimized scheduler to not affect the main runtime that anyone can contribute their system resources to.
distccto Distributed compilationRelevant: https://github.com/icecc/icecream
Relevant: https://github.com/mozilla/sccache (should work for rust-lang)
@kreyren - what are the security implications of "crowdsourcing" the computing resources that anyone could contribute?
I've read it's best if you are in control of the machines running the jobs (makes sense)..
Well in general you should optimize your permission handling so that running processes woudn't have unwanted access.
Needs to be brainstormed, but my approach would be to let the contributors to handle their system and on demand provided a pre-set method e.g. AppImage