try-comm-central doesn't exist

VERIFIED FIXED

Status

Developer Services
General
--
critical
VERIFIED FIXED
6 years ago
3 years ago

People

(Reporter: standard8, Assigned: cshields)

Tracking

Details

(Reporter)

Description

6 years ago
Somewhere in the last few days http://hg.mozilla.org/try-comm-central has disappeared. AFAIK the only bug to update this has been bug 751675, but that hasn't been touched.

I can't find it on http://hg.mozilla.org/, nor can I push to it.
Duplicate of this bug: 755391
FWIW it is safe to ignore past history of this repo, as long as hooks are setup properly, we can just clone it fresh from comm-central.
Assignee: server-ops → server-ops-devservices
Component: Server Operations → Server Operations: Developer Services
QA Contact: phong → shyam
(Assignee)

Comment 3

6 years ago
(In reply to Justin Wood (:Callek) from comment #2)
> FWIW it is safe to ignore past history of this repo, as long as hooks are
> setup properly, we can just clone it fresh from comm-central.

what hooks would that be?  I don't see any trace of it.  :(
Component: Server Operations: Developer Services → Server Operations
(Assignee)

Updated

6 years ago
Component: Server Operations → Server Operations: Developer Services
(Assignee)

Updated

6 years ago
Assignee: server-ops-devservices → cshields
(Reporter)

Comment 4

6 years ago
(In reply to Corey Shields [:cshields] from comment #3)
> (In reply to Justin Wood (:Callek) from comment #2)
> > FWIW it is safe to ignore past history of this repo, as long as hooks are
> > setup properly, we can just clone it fresh from comm-central.
> 
> what hooks would that be?  I don't see any trace of it.  :(

These ones please:

treeclosure
try_mandatory
(Assignee)

Comment 5

6 years ago
Re-cloned, fixed perms, and added hooks.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
V.Fixed

But do we know what happened?
Status: RESOLVED → VERIFIED
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in before you can comment on or make changes to this bug.