MozillaSecurity / MozillaSecurity/FuzzManager
Use ephemeral fuzzing-tc-config checkout instead of permanent repository
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
We currently keep a git clone of fuzzing-tc-config repo and update it using a MozillaPulse trigger. We only care about the repo HEAD, never history, and the data size on disk is very small. There's no value in maintaining the repo state on disk between triggers.
We should remove the clone and use a temporary copy instead on every trigger (eg. using Github tar download). This eliminates one of our uses of persistent instance storage.
Contributor guide
No contributing guide indexed for this repository
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 tracing the MozillaPulse trigger that updates the fuzzing-tc-config checkout and identify where the persistent clone is created and consumed. Replace that stateful path with a temporary GitHub archive copy fetched on each trigger, then verify the trigger still reads the repository HEAD and leaves no persistent checkout behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, python
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100