mozilla-services / mozilla-services/updatebot
Use the Bugzilla component in moz.build files rather than duplicating the info in moz.yaml files
Open
Nobody has claimed this yet.
Easy
Enhancement
P4
- Dominant language
- Python
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Better to avoid the duplication making stuff out of date or out of sync.
Spitballing what we'd need to do to fix this:
- Assert that for libraries we are about initially, a moz.build file is next to the moz.yaml file. If there isn't, rethink this approach...
- In LibraryProvider, find the moz.build file next to the moz.yaml file.
- Do a dumb parse looking for the BUG_COMPONENT associated with Files("**")
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating LibraryProvider and the handling of moz.yaml files, then inspect how adjacent moz.build files expose BUG_COMPONENT for Files("**"). Done means libraries no longer duplicate Bugzilla component data in moz.yaml, and the expected moz.build presence and component lookup are covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100