eagerly upload modified inputs
Open
not stale
P2
team-Remote-Exec
type: feature request
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 72
Description
in order to safe a roundtrip for incremental remote execution builds we should evaluate whether we could make it so that Bazel eagerly uploads files that have changed between builds, including the merkle tree nodes affected.
Contributor guide
Research direction
Start by tracing Bazel's incremental remote execution path and how changed inputs and affected Merkle tree nodes are currently handled. Determine whether eager uploads can avoid a round trip; done requires a concrete, agreed implementation approach and validation for incremental builds.
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
- Needs clarification
- Newbie friendliness
- 25/100