Setting Worker Machine for Distributed Builds
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- build-system, cli, distributed-systems
Research direction
Start with the distributed-build command examples in the issue, then trace how bxl handles /DistributedBuildRole:Worker and the required config.dsc. Document the worker startup command and what configuration the worker should use, making clear which settings remain on the orchestrator.
Written by the indexing model from the issue text.
Description
While using distributed build from Orchestrator machine we specify config file for solution to build using MsBuild like "bxl /config:config.dsc /DistributedBuildOrchestratorLocation:DTP-ABC-IND:9090 /DistributedBuildRole:Orchestrator /DistributedBuildWorker:DTP-XYZ-IND:9090 /DistributedBuildServicePort:9090" and we have set inbound & outbound rule for Port 9090. But how do we initiate worker machine like we need bxl.exe running on worker machine for distributed build. And mainly on worker machine we need command like "bxl /DistributedBuildRole:Worker /DistributedBuildOrchestratorLocation:DTP-ABC-IND:9090" but additionally it asks to specify config.dsc. If so what will we specify in config file on worker machine as worker machine just need to build and all required things are specified in config.dsc file on Orchestrator machine.
- Dominant language
- C#
- Stars
- 1k
- Forks
- 168
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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/BuildXL
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in microsoft/BuildXL
Similar issues
-
:watch: Not Triaged async-task-programming/subsvc dotnet-csharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Python: Bug: AnnotationContent and StreamingAnnotationContent to_element writes CitationType.X, so annotations in a rendered chat history fail to parsePossibly taken A pull request linked to this issue is open or already merged. Openpython triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/semantic-kernel#14590 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Needs-Triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PowerShell/PowerShell#28194 ·
Maintainers usually reply within 1 day
-
AI Projects Client customer-reported needs-team-attention question Service Attention
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Azure/azure-sdk-for-net#63804 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day