Closed Bug 1405688 Opened 8 years ago Closed 8 years ago

Commit access level 1 for Peter Major

Categories

(Infrastructure & Operations :: MOC: Service Requests, task)

Product:
Infrastructure & Operations
Component:
MOC: Service Requests
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jdm, Assigned: Usul)

References

Details

+++ This bug was initially created as a clone of Bug #1405668 +++ I would like to request commit level access level 1 for Peter Major <peter.major@forgerock.com>. He has contributed patches to the Marionette remote protocol and for the future needs access to schedule his own try runs.
account created , added key level1 and hg.
Assignee: nobody → ludovic
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Is there any chance that the account could be tied to my personal e-mail address instead? MozReview seems to think that I don't have access to trigger try builds, could it be because my Bugzilla account has my personal e-mail address as well? (I've only used my corporate e-mail address for my first contribution in Mercurial...).
(In reply to Peter Major from comment #2) > Is there any chance that the account could be tied to my personal e-mail > address instead? MozReview seems to think that I don't have access to > trigger try builds, could it be because my Bugzilla account has my personal > e-mail address as well? (I've only used my corporate e-mail address for my > first contribution in Mercurial...). Not related to bugzilla AFAIK, but more to how you hg config and .ssh/config file look like they contain your keys and identities so check that first.
I'm having difficulty to schedule try builds, and the suggestion is that my L1 access may not be set up correctly. Relevant IRC log: http://logs.glob.uno/?c=mozilla%23mozreview#c27639 Could you reopen this case? Thank you.
Peter, does your ~/.ssh/config contain the new email address as the user for hg.mozilla.org?
Flags: needinfo?(majorpetya)
Level1 was missing i added it.
I believe this is working now (the MozReview UI now tells me that I can't create try builds for closed reviews, but previously it was complaining about scm level), will see when I open my next review. Thanks for your help.
Flags: needinfo?(majorpetya)
You need to log in before you can comment on or make changes to this bug.