Closed Bug 1270624 Opened 9 years ago Closed 7 years ago

Clearly explain BMO API key usage in the docs

Categories

(MozReview Graveyard :: Documentation, defect)

Product:
MozReview Graveyard
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: wlach, Unassigned)

Details

I just submitted a simple patch in bug 1270617, and I wanted to run it through try. However, I didn't see the `automation` menu when I logged in. Just this message: "Git user? Associate your LDAP account with MozReview to use Try integration and Autoland." I figured this meant that I wasn't seeing the automation menu because I needed an API key. So I went to the instructions (https://mozilla-version-control-tools.readthedocs.io/en/latest/mozreview/install.html#manually-associating-your-ldap-account-with-mozreview), which unhelpfully didn't tell me how to generate an API key which was required for ldap association. I found out from mcote that I could go here: https://bugzilla.mozilla.org/userprefs.cgi?tab=apikey However, having done that, I'm still not seeing an automation menu. Does that only work for scheduling try runs after review has been granted, and I have to run them manually first? If so, it would be nice if the UI would tell me that somehow. In sum: 1. The docs should be updated to give instructions on creating API keys 2. It would be nice if the presence/absence of the Automation menu (or whatever it's called) were explained somehow.
Flags: needinfo?(mcote)
The main problem is that the Automation menu is only available from the "Reviews" view, for no good reason that I can think of. This is bug 1232703, and I've assigned it to someone to deal with soon, as it also recently tripped someone up. I'm not sure how you leaped from "Associate your LDAP account" to "need an API key". API keys in fact have nothing specifically to do with LDAP association; they're about Bugzilla integration. Regardless, that message about Git was pretty old, and we removed it a few days ago. But you're right about API keys not being explained particularly well in the documentation, so I will morph this bug into that.
Component: Autoland → Documentation
Flags: needinfo?(mcote)
Summary: try/autoland integration unclear when submitting a patch → Clearly explain BMO API key usage in the docs
MozReview is now obsolete. Please use Phabricator instead. Closing this bug.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.