Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B buck
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 201
    • Issues 201
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Meta
  • buck
  • Issues
  • #2413
Closed
Open
Issue created Mar 12, 2020 by Administrator@rootContributor

Example for Remote Execution

Created by: OleksandrKorniiets

Hi, everyone. First of all, I want to thank the BUCK team for the great documentation and tutorials. Everything is clear and easy to setup at least for basic tasks. Sinking back to the problem - I am trying to understand a more complex setup with remote execution process. I didn't find any references for a configuration when some build actions are sharded across the multiple build agents (similar to Bazel). As I see there is Bazel remote execution code in a thirdparties, so I suspect this feature is present in BUCK also. Am I right? Could somebody please give me a hint?

Assignee
Assign to
Time tracking