1278747 - Set up the bug filer tool using it's own Bugzilla account

Status: RESOLVED FIXED

(Tree Management :: Treeherder, defect)

Description

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

To use the new bug filer tool that was added, we need to set Treeherder up with an API key to a bugzilla account. During testing, I just used my own personal api key on bugzilla-dev, but we need something unique for the actual deployment.

Bug 1110240 suggested we create a bugzilla account with the email address of `[e-mail]`. Once that account is created, we'll need to generate an API key for it at https://bugzilla.mozilla.org/userprefs.cgi?tab=apikey and then add that key into the Treeherder environment (I'm not totally clear how those get set on stage/prod) as `BZ_API_KEY`.


Marking the bug private since we'll likely be disclosing the API key in here.

Comment 1

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

Ed, any idea who can set the account up and configure Treeherder (stage first, I suppose)?

Comment 2

[Ed Morley [:emorley]]

I would:
1) File a non-private bug in bugzilla.mozilla.org::Administration, blocking this one, asking a Bugzilla account to be created with that username, and for them to choose a strong random, which they PM to you (ensuring everyone is connected via a secure IRC connection) rather than pasting in a bug.
2) Log into that Bugzilla account using those credentials and:
 - create an API key
 - Set an appropriate account display name / block needinfo+review requests etc (since followers don't get those, so it just causes false expectation) / set any other appropriate settings
3) File a non-private bug in Tree Management::Infrastructure, blocking this one, asking fubar to set the BZ_API_KEY environment variable on both stage and production, and asking him to PM you on IRC for the API key, rather than pasting in the bug. Since the environment variable doesn't switch anything on per-se (if people aren't using the feature), we can just enable both stage+prod at once.
4) Try out the feature (might as well use prod, since it makes no difference to Treeherder, since the content is ending up in Bugzilla, not Treeherder).
5) PM me on IRC with the Bugzilla account details, so I can add to my password manager, in case we need them in the future. I will also set BZ_API_KEY on the Heroku instances at this point.

Sound ok? :-)

Comment 3

[Ed Morley [:emorley]]

s/strong random/strong random password/