Closed Bug 965547 Opened 11 years ago Closed 11 years ago

Request for a new git repository

Categories

(Developer Services :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mcote, Assigned: fubar)

References

Details

Hi, I need two git repositories created for the impending Bugzilla bzr -> git migration (https://wiki.mozilla.org/Bugzilla:Migrating_to_git). These will eventually be mirrored to github, but we can enable that later. The two repo paths should be * /bugzilla/bugzilla * /bugzilla/bmo There are existing LDAP groups for access to the bzr repos: bzr_bugzilla and bzr_bmo, respectively. I'm not sure if you would want to keep them or create new ones for git access. I don't really know how that part works, although FYI after the migration I want to shut down write access to bzr to all but a handful of accounts. We'll have a script mirroring git to bzr for a while (duration as yet undetermined, but minimum 6 months and probably longer), and that should be the only thing writing to bzr unless we need to fix something.
looks good to me
Assignee: nobody → server-ops-webops
Component: Repos and Hooks → WebOps: Source Control
Product: Release Engineering → Infrastructure & Operations
QA Contact: hwine → nmaul
Version: unspecified → other
Repos created: sekrit$ ssh gitolite3@git.mozilla.org info -lc bugzilla hello klibby@mozilla.com, this is gitolite3@git1 running gitolite3 3.5.1-1.el6 on git 1.7.11.3 R bugzilla/bmo R bugzilla/bugzilla They are currently using the bzr_{bmo,bugzilla} groups for access control (RW; everyone as read access), but I filed bug 967697 for thoughts on replicating them for the above reasons; changing groups down the road only requires a small change to the git config.
Assignee: server-ops-webops → klibby
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
(In reply to Mark Côté ( :mcote ) from comment #0) > although FYI after the migration I want to shut down write access to bzr to > all but a handful of accounts. Do not forget that we still need to be able to tag branches on bzr.
After some discussion, we need the bmo repo moved and a bunch of new repos created. Please move /bugzilla/bmo (which I presume is actually /bugzilla/bmo.git, right?) to /webtools/bmo/bugzilla.git. Please create the following additional repos: /bugzilla/extensions/Browse.git /bugzilla/extensions/browserid.git /bugzilla/extensions/DescribeUser.git /bugzilla/extensions/Developers.git /bugzilla/extensions/ExtraValues.git /bugzilla/extensions/GNOME.git /bugzilla/extensions/PatchReport.git /bugzilla/extensions/ProductInterests.git /bugzilla/extensions/profanivore.git /bugzilla/extensions/requestwhiner.git /bugzilla/extensions/sitemap.git /bugzilla/extensions/StockAnswers.git /bugzilla/extensions/sync.git /bugzilla/extensions/typesniffer.git /bugzilla/extensions/vcs.git /bugzilla/extensions/WeeklyBugSummary.git /bugzilla/extensions/cannedcomments.git /bugzilla/extensions/rest.git /bugzilla/extensions/trackingflags.git /bugzilla/extensions/InlineHistory.git /bugzilla/extensions/securemail.git /bugzilla/extensions/splinter.git /bugzilla/extensions/testopia.git /bugzilla/misc/active-installs.git /bugzilla/misc/bugzilla-bugbot.git /bugzilla/misc/build.git /bugzilla/misc/landfill.git /bugzilla/misc/tinderbox-bugbot.git /bugzilla/misc/tinderbox-client.git /bugzilla/qa.git /webtools/bmo/qa.git Thanks!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Mark Côté ( :mcote ) from comment #4) > /bugzilla/extensions/GNOME.git Could someone remind me why we host GNOME customizations and some other extensions which seem to be totally unmaintained??
Flags: needinfo?(bugzilla-mozilla)
Repos created. sekrit$ ssh gitolite3@git.mozilla.org info | egrep 'bugzilla|bmo' R bugzilla/bugzilla R bugzilla/extensions/Browse R bugzilla/extensions/DescribeUser R bugzilla/extensions/Developers R bugzilla/extensions/ExtraValues R bugzilla/extensions/GNOME R bugzilla/extensions/InlineHistory R bugzilla/extensions/PatchReport R bugzilla/extensions/ProductInterests R bugzilla/extensions/StockAnswers R bugzilla/extensions/WeeklyBugSummary R bugzilla/extensions/browserid R bugzilla/extensions/cannedcomments R bugzilla/extensions/profanivore R bugzilla/extensions/requestwhiner R bugzilla/extensions/rest R bugzilla/extensions/securemail R bugzilla/extensions/sitemap R bugzilla/extensions/splinter R bugzilla/extensions/sync R bugzilla/extensions/testopia R bugzilla/extensions/trackingflags R bugzilla/extensions/typesniffer R bugzilla/extensions/vcs R bugzilla/misc/active-installs R bugzilla/misc/bugzilla-bugbot R bugzilla/misc/build R bugzilla/misc/landfill R bugzilla/misc/tinderbox-bugbot R bugzilla/misc/tinderbox-client R bugzilla/qa R webtools/bmo/bugzilla R webtools/bmo/qa
This was done and tested.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
(In reply to Frédéric Buclin from comment #5) > (In reply to Mark Côté ( :mcote ) from comment #4) > > /bugzilla/extensions/GNOME.git > > Could someone remind me why we host GNOME customizations and some other > extensions which seem to be totally unmaintained?? I thought having everything upstream was best. It seems unmaintained because I'm stumped at porting the attachment status bit. I don't know how to proceed. Now that it is in git, I could also put them on git.gnome.org if wanted? Just seems best to have all the extensions together?
Flags: needinfo?(bugzilla-mozilla)
Component: WebOps: Source Control → General
Product: Infrastructure & Operations → Developer Services
You need to log in before you can comment on or make changes to this bug.