Closed
Bug 981873
Opened 11 years ago
Closed 11 years ago
Request for a new git repository: "fuzz-tools" (public)
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jruderman, Assigned: u429623)
References
Details
I would like:
a) a new git repository on git.mozilla.org commitable by the fuzzing team
b) a world readable mirror of that on github.com/mozilla
> https://wiki.mozilla.org/ReleaseEngineering/RepositoryCreationRequest
> what commit access level is required
git.mozilla.org:
Write: Jesse Ruderman, Gary Kwong, Christian Holler, Christoph Diehl, Chris AtLee
Read: Everyone, if possible.
At least 'ffxbld' (see bug 526888) and 'fuzzbots' (see bug 912265)
github:
Write: Only the mirroring bot should be pushing. Public issues.
Read: Everyone
> the purpose of the repository
I will move the PUBLIC parts of our old hg fuzzing repo (bug 424021) to this new repo.
This repo will contain fuzzing harness code, along with testing tools that can also be used on their own, such as Lithium (testcase reducer) and autobisect-js (regression pinpointer).
> which product(s) it will ship as part of (if any)
No end-user software will contain bits from here.
Some releng slaves will continuously pull code from the git.mozilla.org repo and run it, so I do want write access to be reasonably secure :)
The git.mozilla.org has been available for use since bug 982157 was closed -- my apologies for not making that clear.
This bug remains open for establishing the read only mirror on github.
Assignee: nobody → hwine
r/o repo created @ https://github.com/mozilla/automation-fuzz-tools.git
next step: hooking up mirroring plumbing
in production via http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/350287e50441
Note: there is nothing in the repo on git.mozilla.org yet. Once you push something to git.m.o, please verify it shows up on github (within 15 minutes). Reopen if there are issues at that point.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Release Engineering → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•