Create a new repository on git.mozilla.org

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
5 years ago
7 months ago

People

(Reporter: gal, Assigned: hwine)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
We are standing up a "plan b" hg mirror on g.m.o. Please create the repository /gecko.git and grant Ehsan access to the repo at the filesystem level, and system access as necessary. Ehsan, can you please specify what exactly you need?

Please don't act on this bug until mrz had a chance to see/approve this request.
(Reporter)

Updated

5 years ago
Flags: needinfo?(mrz)

Updated

5 years ago
Assignee: server-ops → nobody
Component: Server Operations → Release Engineering: Developer Tools
QA Contact: shyam → hwine

Updated

5 years ago
Summary: access to g.m.o → Create a new repository on git.mozilla.org

Comment 1

5 years ago
We also need another helper repository, which can be called mozilla-history-tools.git.  I need write access on both repos under my LDAP account (eakhgari@m.c).  I will try to push to these repos remotely, and will file a new bug if I end up needing ssh access to the git server.

We also need another server for running the update scripts to keep the repo updated, which I think we need to file another bug for, but that can be step 2 and we can keep gecko.git updated using my current scripts.  We need to have somebody take over monitoring the update scripts once they're moved to Mozilla infrastructure.  I can work with them to get the up to speed when someone gets assigned to this task.
(Assignee)

Comment 2

5 years ago
Update: per phone conversations with agal, bmoss, & joduinn, releng is going to populate releases/gecko.git with the current copy of github:mozilla/mozilla-central and update from there.

We will also be working the original "plan a" with an decision point Monday am (Nov 12)

Also, we'll be adding in to the repos the tracker branches (based on gecko versions) requested by agal (which no repo has atm).

Bottom line: no gecko.git repository will be created, releng will be populating the releases/gecko.git repo.
Assignee: nobody → hwine
Status: NEW → ASSIGNED
Flags: needinfo?(mrz)
(Assignee)

Comment 3

5 years ago
closing - "plan a" worked,
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering

Updated

4 years ago
Blocks: 936535
(Assignee)

Updated

4 years ago
No longer blocks: 936535
Component: Tools → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.