bazelbuild / bazelbuild/bazel

Distribute WorkRequestHandler to maven central

Open
#19,544 3 comments 1 reaction 0 assignees View on GitHub
help wanted P3 team-Performance type: feature request
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 18h
Merged PRs (30d)
75

Description

### Description of the feature request:

Bazel has a robust feature rich [worker implementation](https://github.com/bazelbuild/bazel/blob/d9beda5b4f6ce8d2b8d574da5d4362c7b211f243/src/main/java/com/google/devtools/build/lib/worker/WorkRequestHandler.java) baked into it. Exposing it as a Bazel tool or distributing it to maven central would eliminate the need for rule maintainers to build their own workers from scratch.

A few examples of projects that have had to build their own worker implementations: [Intellij](https://github.com/bazelbuild/intellij/issues/3685), [rules_kotlin](https://github.com/bazelbuild/rules_kotlin/tree/master/src/main/kotlin/io/bazel/worker), [rules_detekt](https://github.com/buildfoundation/bazel_rules_detekt/blob/master/detekt/wrapper/src/main/java/io/buildfoundation/bazel/detekt/execute/WorkerExecutable.java).

Contributor guide

Open the contributing guide

Research direction

Start by reading src/main/java/com/google/devtools/build/lib/worker/WorkRequestHandler.java and the linked examples from IntelliJ, rules_kotlin, and rules_detekt. Determine whether the intended deliverable is a Bazel tool or a Maven Central artifact; done means rule maintainers can consume the shared worker implementation without rebuilding it themselves.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.