Create new build event ID type for external repositories
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 72
Description
### Description of the feature request:
https://github.com/bazelbuild/bazel/blob/1f4aa9e65a5086a59ced0ecb1a6123c5bc772dda/src/main/java/com/google/devtools/build/lib/repository/RepositoryFailedEvent.java#L48-L59
The current event id is a label looks like `label: "//external:+_repo_rules+remote"`, we should avoid using `EXTERNAL_PACKAGE_IDENTIFIER` anymore.
### Which category does this issue belong to?
_No response_
### What underlying problem are you trying to solve with this feature?
_No response_
### Which operating system are you running Bazel on?
_No response_
### What is the output of `bazel info release`?
_No response_
### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.
_No response_
### What's the output of `git remote get-url origin; git rev-parse HEAD` ?
_No response_
### Have you found anything relevant by searching the web?
_No response_
### Any other information, logs, or outputs that you want to share?
_No response_
Contributor guide
Research direction
Start with src/main/java/com/google/devtools/build/lib/repository/RepositoryFailedEvent.java at lines 48-59, then trace uses of EXTERNAL_PACKAGE_IDENTIFIER and the current event ID. Define the required replacement event ID type for external repositories and verify that this event no longer uses the existing external package identifier.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100