Closed Bug 924719 Opened 11 years ago Closed 11 years ago

new git.m.o repository: integration/gecko-dev.git

Categories

(Developer Services :: General, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mozilla, Unassigned)

References

Details

Similar to bug 917071, these should have receive.denyDeletes & receive.denyNonFastForwards set to True; per https://bugzilla.mozilla.org/show_bug.cgi?id=917071#c1 that probably means

repo integration/gecko-dev
    RW+     =   vcs-sync@mozilla.com
    R       =   @all
    config  receive.denyNonFastforwards = true
    config  receive.denyDeletes         = true


Assigning to Hal first, for signoff and to make sure I didn't miss anything.
Hal: could you doublecheck my request and unassign yourself (or assign to the appropriate person) if it's accurate?
Aki - we (you) can create this repo simply by referencing it as user vcs-sync. (e.g. a pull or clone should create it.) Then IT can set the additional configuration values. So, back to you to create repo, then direct to IT for config changes.

Question: is it now true that we'd want these two config values set on all converted/mirrored repos? (Those under release/*, integration/*, b2g/*, external/*.) If so, we could file an additional request for that. (I'm not sure if git-o-lite supports that, but worth an ask, if we want it most of the time.)
Assignee: hwine → aki
Flags: needinfo?(aki)
Am I doing something wrong?

+ export GIT_SSH_KEY=/home/vcs2vcs/gd3-ssh/vcs-sync_rsa
+ GIT_SSH_KEY=/home/vcs2vcs/gd3-ssh/vcs-sync_rsa
+ export GIT_SSH=/opt/vcs2vcs/mozharness/external_tools/git-ssh-wrapper.sh
+ GIT_SSH=/opt/vcs2vcs/mozharness/external_tools/git-ssh-wrapper.sh
+ git clone git+ssh://gitolite3@git.mozilla.org/integration/gecko-dev.git
Initialized empty Git repository in /home/vcs2vcs/test/gecko-dev/.git/
FATAL: R any integration/gecko-dev vcs-sync@mozilla.com DENIED by fallthru
(or you mis-spelled the reponame)
fatal: The remote end hung up unexpectedly
Flags: needinfo?(aki) → needinfo?(hwine)
(In reply to Aki Sasaki [:aki] from comment #2)
> Am I doing something wrong?

No, I did -- I trusted my memory.

This is our first integration/* repo, so there is no "wild repo" configured for it. (I mistakenly thought there was.)

Two options at this point:
 1. send to IT as original (i.e. just reset "assigned to"), and let it be a one off
 2. if we will have more repos to live under integration/*, ask for that to be added to "wild repo" list.

If we're not sure, #1 is best way forward, while we sort out #2.
> 
> + export GIT_SSH_KEY=/home/vcs2vcs/gd3-ssh/vcs-sync_rsa
> + GIT_SSH_KEY=/home/vcs2vcs/gd3-ssh/vcs-sync_rsa
> + export GIT_SSH=/opt/vcs2vcs/mozharness/external_tools/git-ssh-wrapper.sh
> + GIT_SSH=/opt/vcs2vcs/mozharness/external_tools/git-ssh-wrapper.sh
> + git clone git+ssh://gitolite3@git.mozilla.org/integration/gecko-dev.git
> Initialized empty Git repository in /home/vcs2vcs/test/gecko-dev/.git/
> FATAL: R any integration/gecko-dev vcs-sync@mozilla.com DENIED by fallthru
> (or you mis-spelled the reponame)
> fatal: The remote end hung up unexpectedly
Flags: needinfo?(hwine)
Looks like we're back to comment 0 :)
Assignee: aki → server-ops-webops
Blocks: 847727
No longer blocks: 847227
All set; let me know if you run into any issues.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Thank you!
Status: RESOLVED → VERIFIED
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.