bazelbuild / bazelbuild/bazel

Feature request: --show-rulekey

Open
#7,962 53 comments 71 reactions 0 assignees View on GitHub
not stale P2 team-Core type: feature request
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 20h
Merged PRs (30d)
72

Description

### Description of the problem / feature request:

Buck has the concept of [rule keys](https://buckbuild.com/concept/rule_keys.html), which we can obtain by running `buck targets --show-rulekey //...`. We'd love to see similar feature in Bazel.

### Feature requests: what underlying problem are you trying to solve with this feature?

We need to see what targets are changed, thus need to rebuilt and test, from one revision to another. In order to [keep master green at scale](https://dl.acm.org/citation.cfm?id=3303970), we need to build and test diffs in parallel. Getting the rule key for each target help us decide what diffs are independent and safe to build and test in parallel.

Contributor guide

Open the contributing guide

Research direction

Start by reading the linked rule-key concept and comparing Bazel's target behavior with Buck's `buck targets --show-rulekey //...` command. Define how Bazel should expose a rule key for each target and verify that the output supports identifying changed targets for parallel build and test decisions.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.